Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: ncurses announcement - trial run
X-MimeOLE:	Produced By Microsoft Exchange V6.0.4417.0
Date:	Thu, 20 Sep 2001 13:03:56 +1000
Message-ID:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08F1A8@itdomain002.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	ncurses announcement - trial run
Thread-Index:	AcFBgANe8/8Cj7NlSeWKBqHMC3JfWAAAI3hQ
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc:	<cygwin-apps AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id WAA16409

> -----Original Message-----
> From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu]
> 
> 
> Robert Collins wrote:
> 
> > Should the man pages be in with the .dlls? Or at least the 
> end user ones
> > that refer to setting TERM etc?
> 
> 
> I was just following the lead of the other distros RPMS. 
> Besides, what 
> you suggest would cause conflicts -- both libncurses5 and libncurses6 
> would contains these man pages, leading to ordering problems with 
> upgrades (Or, forcing me to update libncurses6 MERELY because 
> libncurses7 is coming out -- update 6 so NOT include those man pages. 
> But then you STILL have ordering problems.)

Ah, yes I see that now :[.

> > Could the static library and header tarball be called 
> ncurses-dev-5.2-6
> > ? (I hope the reason is obvious :})
> 
> 
> 'ncurses-devel' package -- but decided to let necessity be my 
> guide -- 

fair enough. Only askin'.

> That's up to Chris.  Having just pestered him to release a 
> new version 
> with Ralf's fix, I'd prefer to wait before (a) bugging him again (b) 
> slamming the mirrors with Yet Another Update.  Besides, there's a few 
> more items on the TODO list for binutils; it'd be nice to 
> push some of 
> that thru before the next binutils rev.

I guess the other option, if you want to avoid the folk-who-cannot-read
problem is to hold off for the next binutils and do the above then. (But
I'm sure you've already considered that).

Rob

- Raw text -