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 5/13/2017 7:12 AM, Jon Turney wrote:
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.

Yes, that was my first thought. But there's no longer a source file for the obsolete package[1], and cygport complains that SRC_URI must be defined. Maybe cygport should be patched to allow an empty SRC_URI when the category is _obsolete. Or do you see another way around this?


The package in question is texlive-collection-htmlxml, which no longer exists upstream.

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