This is the mail archive of the
mailing list for the Cygwin project.
Re: [RFD] ncurses update
- To: cygapp <cygwin-apps at cygwin dot com>
- Subject: Re: [RFD] ncurses update
- From: Corinna Vinschen <cygwin-apps at cygwin dot com>
- Date: Mon, 17 Sep 2001 18:29:15 +0200
- References: <3BA3A5F4.firstname.lastname@example.org>
On Sat, Sep 15, 2001 at 03:03:16PM -0400, Charles Wilson wrote:
> This is an ABI change, requiring the DLL number to be bumped, and apps
> to be recompiled. (e.g. we now have cygncurses6.dll, etc)
Somehow I don't like the `6' here for a ncurses-5.2 version but
if we can't avoid that...
> What do you think about the following?
> a) the --enable-auto-import change to ncurses (and its related 'bump the
> DLL number requirement)
If it works, it's ok with me.
> b) the new libncurses5 package? (should I just put the old DLLs inside
> ncurses-5.2-6 package? should the new DLL's themselves be split from
> the ncurses package and put in libncurses6 package?) What about the
> source code naming difference (libncurses5 != ncurses)?
Splitting is ok but what about just naming the file `ncurses5-5.2-1'?
The package would be nearer to the other ncurses package in setup's
> c) splitting the terminfo package (and forking the source code) For:
> allows me to update the terminfo database more frequently and easier.
> Against: forking is bad.
Forking is good here.
Q: If I have installed the new ncurses package and I want to
rebuild e.g. tcsh, do I have to change my Makefile? Do I have
to change anything?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.