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: The Cygwin Mailing List <cygwin at cygwin dot com>
- Cc: Ken Brown <kbrown at cornell dot edu>
- Date: Mon, 15 May 2017 16:56:28 +0100
- Subject: Re: Making a package obsolete
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On 15/05/2017 15:30, Ken Brown wrote:
On 5/14/2017 1:38 PM, Jon Turney wrote:
On 13/05/2017 20:44, Ken Brown wrote:
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
be distributed among several other packages. So I can't handle
defining OBSOLETES in any one .cygport file. Is there a standard
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,
it's category to _obsolete, make it's contents empty, and make it
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, 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?
I would think you can use the same SRC_URI as previously, but set
PKG_CONTENTS="" and PKG_IGNORE="*" ?
You're right, I can do something like that. I was being overly pedantic
in wanting SRC_URI to be "accurate". Sorry for the noise.
You can always make an empty tarball called
texlive-collection-htmlxml-20170515.tar.xz or whatever, and use that for
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple