Making a package obsolete

Ken Brown kbrown@cornell.edu
Mon May 15 17:21:00 GMT 2017


On 5/15/2017 12:51 PM, szgyg wrote:
> On Mon, May 15, 2017 at 12:20:46PM -0400, Ken Brown wrote:
>> On 5/15/2017 11:56 AM, Jon Turney wrote:
>>> You can always make an empty tarball called
>>> texlive-collection-htmlxml-20170515.tar.xz or whatever, and use that for
>>> SRC_URI.
>>
>> Good idea, thanks.  But it turns out that there's another problem: cygport
>> won't actually create an empty binary tarball in this situation.
>>
>> The relevant code is in pkg_pkg.cygpart around lines 149--163, especially
>> this part:
>>
>> 		elif (( pkg_count == 1 ))
>> 		then
>> 			pkg_contents="*"
>> 		else
>> 			pkg_contents=
>>
>> We get here if PKG_CONTENTS is unset or empty.  (There's actually no test to
>> see if it's set but empty.)  In the situation under discussion, this results
>> in pkg_contents="*" followed by a tar error.
>>
>> Yaakov, shouldn't the user be allowed to explicitly set PKG_CONTENTS empty
>> and have cygport honor that, at least for obsolete packages?
>
> I've used the attached files to create an empty, dependencies-only package.

Yes, that works around the problem by not actually creating an empty 
binary tarball.  But I still think cygport should allow the creation of 
an empty binary tarball by a set but empty PKG_CONTENTS.

Ken



More information about the Cygwin-apps mailing list