From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Dropping requires: from setup.ini?
Date: Fri, 2 Sep 2022 14:56:34 +0100 [thread overview]
Message-ID: <3e2129ee-393c-a9a3-5747-ae870d2e62d4@dronecode.org.uk> (raw)
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
next reply other threads:[~2022-09-02 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 13:56 Jon Turney [this message]
2022-09-06 5:46 ` Achim Gratz
2022-10-02 16:09 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e2129ee-393c-a9a3-5747-ae870d2e62d4@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).