Dropping requires: from setup.ini?

Dropping requires: from setup.ini?

[Jon Turney]

Perhaps it's time to consider dropping the requires: line from setup.ini?

requires: contains the union of dependencies for all package versions 
(long ago, it was the dependencies for the current package version, and 
the dependencies for other versions were not available to setup, with 
hilarious consequences...)

requires: is superfluous to depends2:, which versions of setup since 
2.888 (Feb 2018) understand, but there may be some other 3rd-party tools 
which still rely on it.

Dropping it also reduces the size of setup.ini by about 5%.

(See [1] for an example of the confusion it's continued existence can cause)

(setup versions <2.903 are precluded from trying to use a current 
setup.ini, by a combination of changed signing key and policy mechanisms 
inside setup)

[1] https://cygwin.com/pipermail/cygwin/2022-February/250949.html

Re: Dropping requires: from setup.ini?

[Achim Gratz]

Jon Turney writes:
> Perhaps it's time to consider dropping the requires: line from setup.ini?

I guess the only way to find out is to actually do it and see who
complains…  maybe if Cygwin 3.4 is imminent that update would be a good
time to make that change.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: Dropping requires: from setup.ini?

[Jon Turney]

On 06/09/2022 06:46, Achim Gratz wrote:
> Jon Turney writes:
>> Perhaps it's time to consider dropping the requires: line from setup.ini?
> 
> I guess the only way to find out is to actually do it and see who
> complains…  maybe if Cygwin 3.4 is imminent that update would be a good
> time to make that change.
I have deployed this change.

I'd rather not couple it to something else unnecessarily, especially as 
I'll have other problems to worry about when we get around to dropping 
x86 packages after 3.4...