On Jul 6 14:27, Andrew Schulman wrote: > Question: what should I do about these obsolete packages? I could release > new setup.hints for them with category: _obsolete, but would that force users > to uninstall them the next time they updated? I don't want to maintain those > packages any more, but I don't want to force users to uninstall them either.
I don't think you need to worry. setup won't force users to uninstall packages when they become obsoleted. Just send new setup.hint files, I will move the packages in the _obsolete subdir then. > # unison2.27 > wget \ > http://home.comcast.net/~andrex/cygwin/unison2.27/setup.hint \ > > http://home.comcast.net/~andrex/cygwin/unison2.27/unison2.27-2.27.29-1.tar.bz2 > \ > > http://home.comcast.net/~andrex/cygwin/unison2.27/unison2.27-2.27.29-1-src.tar.bz2 > # unison2.17 > wget \ > > http://home.comcast.net/~andrex/cygwin/unison2.17/unison2.17-2.17.1-2.tar.bz2 > \ > > http://home.comcast.net/~andrex/cygwin/unison2.17/unison2.17-2.17.1-2-src.tar.bz2 > # unison2.13 > wget \ > > http://home.comcast.net/~andrex/cygwin/unison2.13/unison2.13-2.13.16-2.tar.bz2 > \ > > http://home.comcast.net/~andrex/cygwin/unison2.13/unison2.13-2.13.16-2-src.tar.bz2 Uploaded. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
