This is the mail archive of the
mailing list for the Cygwin project.
Re: Making a package obsolete
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: cygwin-apps at cygwin dot com
- Cc: Ken Brown <kbrown at cornell dot edu>
- Date: Sat, 13 May 2017 12:12:44 +0100
- Subject: Re: Making a package obsolete
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com>
On 12/05/2017 22:02, Ken Brown wrote:
I have a package that is going to become obsolete, but its contents will
be distributed among several other packages. So I can't handle this by
defining OBSOLETES in any one .cygport file. Is there a standard way to
deal with this using cygport, or should I just create the necessary
tarballs and .hint file manually?
I think the best way to do that is to bump your package revision, change
it's category to _obsolete, make it's contents empty, and make it depend
on the packages which are replacing it.