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: Making a package obsolete


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.


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