Wed Apr 5 22:42:00 GMT 2017
On 05/04/2017 21:55, Marco Atzeri wrote:
> On 04/04/2017 19:38, Jon Turney wrote:
>> On 04/04/2017 14:28, Marco Atzeri wrote:
>>> Not sure if "calm" is excluding them, but I noticed for some
>>> packages we have now an excess of "setup.hint" as all existing
>>> revision have their own package-revison.hint
>> These old setup.hint files should be benign, unless they are recording
>> obsolete dependencies which aren't needed any more.
> I assume there is already some case, but I will need to check
> to show some evidence.
Actually, after looking at the code today, I think in the case where the
setup.hint is obsolete, it doesn't contribute anything to dependencies,
but I'd need to test that to be sure...
Anyhow, I worked out a relatively simple way to clean these up, so I
will do that.
>>> Is a cleaning needed ?
>> Eventually, yes.
>> Unfortunately, a maintainer removing these files via '-setup.hint' is
>> not permitted, as I haven't implemented it due to the complexity of
>> determining if that is safe.
>> I've noted that there needs to be a migration plan for this (See )
>> I guess the first stage of which is to turn off uploads containing
>> setup.hint (as generated by older versions of cygport), but I'm not sure
>> we've reached that point in time, yet.
>>  https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
> I assume we are all using latest cygport and uploading only
Yes, one would assume that, but it turns out not to be the case :)
More information about the Cygwin-apps