This is the mail archive of the
mailing list for the Cygwin project.
per-version hints proposal
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 20 Jun 2016 16:28:06 +0100
- Subject: per-version hints proposal
- Authentication-results: sourceware.org; auth=none
Currently, the setup.hint file is shared between all versions.
This means that manual intervention (by the package maintainer, or on
sourceware) is needed when versions have different dependencies.
To automate this problem out of existence, I suggest replacing the
setup.hint file in an upload with a package-version-release.hint file.
This will be basically identical to the existing setup.hint, with the
advantage that it can't be trampled on by a future version, with the
* 'skip' doesn't seem meaningful on a per-version basis. Since it seems
we can automatically detect packages which should have this applied
anyhow (see the discussion in ), I'd suggest ignoring this hint, to
be retired at some future date.
* 'curr', 'prev' and 'test' don't make sense on a per-version basis. So
I suggest a separate file for these version overrides (versions.hint?)
cygport will be updated to create a pvr.hint rather than setup.hint
calm will be changed so that:
* The requires: line written in setup.ini will contain the union of the
requires: from each pvr.hint
* The sdesc:, ldesc:, category: and message: lines in setup.ini will be
taken from the pvr.hint for the curr version
* While it's already effectively mandatory that a package has a curr
version, this requirement will be documented and enforced.
* The source: line in setup.ini for a package version will consider any
external-source: from the corresponding pvr.hint
* Uploads with a setup.hint will continue to work as before, for a
No setup changes are required.
Immediately, this avoids the need for manual intervention when versions
have different dependencies, and going forward, this is lays some
groundwork for supporting per-version dependencies.