This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 2nd summary (was Re: [HEADSUP] ALL Maintainers, please reply.)


On Sep 27 01:46, Igor Pechtchanski wrote:
> On Tue, 27 Sep 2005, Christopher Faylor wrote:
> > On Mon, Sep 26, 2005 at 11:19:36PM -0400, Charles Wilson wrote:
> > >I've got a new release of ncurses which contains /usr/bin/clear.exe
> > >ready to go (but not yet copied into /release).
> > >
> > >Go ahead an put an empty clear package up on sources (clear-1.0-2 ?) and
> > >we'll let that propagate, and then I'll move my new ncurses over to
> > >release/.
> >
> > I know that there was some talk of releasing an empty clear package but
> > I don't see how that would be useful.  If I do that then we stand the chance
> > of eliminating clear.exe when the clear package is "updated", meaning that
> > we could conceivably remove the clear.exe that ncurses installed.
> >
> > I think the only thing we can do is remove clear from the distribution.
> 
> Actually, it's the other way around.  If the new (empty) clear package and
> the new ncurses are pushed to the mirrors together, the ownership of
> clear.exe goes to ncurses.  Whenever both are installed, both will be
> upgraded, thus "moving" clear.exe to ncurses.

I've uploaded new empty clear packages.  I've not put the clear package
into the _obsolete category so far.  Can I do this already?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]