From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: setup and 'provides:'
Date: Tue, 09 Oct 2018 18:01:00 -0000 [thread overview]
Message-ID: <87va6bvw25.fsf@Rainer.invalid> (raw)
In-Reply-To: <20db3d86-bd80-fe49-4d7d-8b14d49666a7@cornell.edu> (Ken Brown's message of "Mon, 8 Oct 2018 21:31:51 +0000")
Ken Brown writes:
>>> So we'd need to bolt on a feature space in setup as well.
>
> I'm not sure what you mean by this. setup doesn't need to know whether a
> requirement is a feature or a package. It simply passes the dependencies (and
> the provides) to libsolv, which handles them just fine.
If we have features, then setup would need to show them somewhere and it
would be awkward if that info was empty for most packages. Then people
will want to install features instead of packages anyway, so that is
another nudge into "featurizing" the whole distribution. In other
words, once we start using "provides:" in that way, I think it should
become mandatory.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2018-10-09 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 22:02 Ken Brown
2018-10-08 14:41 ` cyg Simple
2018-10-08 15:05 ` Ken Brown
2018-10-08 15:17 ` cyg Simple
2018-10-08 16:24 ` Ken Brown
2018-10-09 15:11 ` cyg Simple
2018-10-09 17:32 ` Ken Brown
2018-10-09 18:03 ` Achim Gratz
2018-10-08 18:07 ` Ken Brown
2018-10-08 20:04 ` Achim Gratz
2018-10-08 21:31 ` Ken Brown
2018-10-09 18:01 ` Achim Gratz [this message]
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=87va6bvw25.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).