From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: [RFC] calm, setup: per-version requires
Date: Sun, 05 Nov 2017 07:35:00 -0000 [thread overview]
Message-ID: <87375tmb55.fsf@Rainer.invalid> (raw)
With the possibility of having more than three versions in setup.ini and
per-version hint files, the need for per-version requires is getting
more urgent. Currently the requires from the corresponding hint files
get merged, which leads to abominations like these (from mosh):
requires: … libprotobuf13 libprotobuf14 libprotobuf8 …
I suggest that the current requires: line is kept to contain the
intersection of all hint files and an additional requires: line in each
version group lists the relative complement of the corresponding hint
file and the non-versioned requires: line. It may be necessary to
rename the requires: token to something else in order to ease parsing,
maybe something like requires+: to show that these are in addition to
the usual requires: line?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next reply other threads:[~2017-11-05 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 7:35 Achim Gratz [this message]
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
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=87375tmb55.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).