This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [RFC] 1.7 Packaging: Obsolete packages
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 21 Aug 2008 12:35:26 +0200
- Subject: Re: [RFC] 1.7 Packaging: Obsolete packages
- References: <48880879.5050400@users.sourceforge.net> <20080724094313.GG5251@calimero.vinschen.de> <488913D9.8070809@users.sourceforge.net> <20080725094034.GR5251@calimero.vinschen.de> <20080730121815.GM29031@calimero.vinschen.de> <48ACED44.4060902@users.sourceforge.net> <20080821082602.GE29104@calimero.vinschen.de>
- Reply-to: cygwin-apps at cygwin dot com
On Aug 21 10:26, Corinna Vinschen wrote:
> On Aug 20 23:21, Yaakov (Cygwin Ports) wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Corinna Vinschen wrote:
> > > What if we add an "obsoletes:" line to setup.{ini,hint}?
> > >
> > > The idea is that you don't have to provide empty replacement packages
> > > for the old packages anymore, and setup removes all packages noted in
> > > the "obsoletes:" line before installing the new package, in the same
> > > step as when replaing old versions of the same package.
> > >
> > > Would that work? Wouldn't that ease the transition to new package
> > > schemes a lot?
> >
> > Any progress yet on this one?
>
> Unfortunately not. The package management in setup is written in some
> sort of martial-arts C++, which I have trouble to follow through. For
> this and for the problem I describe in
>
> http://cygwin.com/ml/cygwin-apps/2008-08/msg00162.html
>
> I would need help.
Setup.exe apparently already understands package lists in setup.ini
which start with "Replaces:" (upper case R), collects the information
and stores it in an internal list, but then doesn't seem to use it
later on. Too bad.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat