From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] calm, setup: per-version requires
Date: Tue, 05 Dec 2017 18:15:00 -0000 [thread overview]
Message-ID: <87tvx5kpnt.fsf@Rainer.invalid> (raw)
In-Reply-To: <0ec636c4-81b8-dc5a-97e9-9147474d8792@dronecode.org.uk> (Jon Turney's message of "Tue, 5 Dec 2017 14:32:52 +0000")
Jon Turney writes:
> prior to 2.880: Will ignore 'depends:', so 'requires:' needs to
> remain the union of dependencies for the benefit of these versions of
> setup.
If you want to maintain backwards compatibility. I am still sitting on
the fence on that, but I currently lean to propose a clean cut and
producing a setup.ini file for backwards compatibility for some time in
parallel with some new file that uses the new syntax only.
> 2.880 onwards: The curr: version will get the union of 'depends:' and
> 'requires:', other versions will get 'requires:'.
That doesn't make any sense, since the requires would be the union of
all depends already. So, 2.880+ should ignore the requires: and use the
union of [curr] and any version specific depends:. But maybe I
misunderstood what you want to be doing.
> The prereq checker checks that the dependencies are satisfied
> (including any version relation), but then installs the 'curr:' or
> 'test:' version (depending on chooser preference) imagining that will
> satisfy it.
>
> libsolv-based: 'depends:' supersedes 'requires:', installs the right
> right thing (hopefully :))
Wait… I thought libsolve-based was 2.880+?
Again the note that the libsolve-based setup.ini format should include a
way to provides: a named feature that other packages can then depends:
on.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2017-12-05 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 7:35 Achim Gratz
2017-11-09 14:27 ` Jon Turney
2017-11-09 18:18 ` Achim Gratz
2017-12-05 14:32 ` Jon Turney
2017-12-05 18:15 ` Achim Gratz [this message]
2017-12-11 19:08 ` 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=87tvx5kpnt.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).