From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] calm, setup: per-version requires
Date: Thu, 09 Nov 2017 14:27:00 -0000 [thread overview]
Message-ID: <b622969c-afb3-6374-62ac-00ce26f18f65@dronecode.org.uk> (raw)
In-Reply-To: <87375tmb55.fsf@Rainer.invalid>
On 05/11/2017 07:34, Achim Gratz wrote:
> 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
Since it's been needed since ~2000, it could hardly be less urgent :)
> 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
Yeah, I guess we could generate requires: line in each version section
now, and this might work with current setup. I don't think this did
anything useful prior to [1] being fixed.
[1]
https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/setup.git;a=commitdiff;h=78e4c7d7c8be4698d362d204aacfe701f6503359;hp=60b4f6caa5c0bcadaf304620a31e37f77f56b9bf
> 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?
The libsolv branch implements per-version '[dD]epends:' headers as per
[2] (which may also contain a version relation)
[2] https://sourceware.org/cygwin-apps/setup.ini.html
next prev parent reply other threads:[~2017-11-09 14:27 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 [this message]
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=b622969c-afb3-6374-62ac-00ce26f18f65@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).