From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] Global Systemd USE Flag
Date: Wed, 8 Aug 2012 10:47:14 -0400 [thread overview]
Message-ID: <CAGfcS_k3B59JoLW-PyjUQ7MrxxaCv=+FXzjGH6Th47AZ1vP1pQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oB9tA99OEYOALH2bkc0x-qGc9GL1eaEdW6PP9NE05cYA@mail.gmail.com>
On Wed, Aug 8, 2012 at 10:38 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> On Wed, Aug 8, 2012 at 4:36 PM, Michał Górny <mgorny@gentoo.org> wrote:
>> We aren't going to add USE flags which don't do anything. That topic
>> was discussed a thousand times, and rising it once more won't change
>> our decision.
>>
>> Similarly, bash-completion flag will be gone at some point.
>
> Everyone has bash. Not everyone has systemd.
>
Then why does OpenRC go out of its way to avoid depending on bash?
The answer is that not everybody has bash.
In any case, this has been discussed on -dev before. The reason that
the unit files were not made a use flag was that they're just simple
text files that don't take much space and don't do anything unless you
use systemd. Having a USE flag to trigger their install doesn't have
much of a point, and it also means that to switch to systemd you'd
have to re-emerge anything that installs a unit file.
If we went this route we'd end up adding an openrc use flag for
anything that sticks files in /etc/init.d, bash-completion, and
probably a bunch of other stuff as well.
If a package is pulling in dependencies that is a different story, but
if we're just talking about a text file I think a USE flag is
overkill.
Rich
next prev parent reply other threads:[~2012-08-08 14:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 13:11 [gentoo-dev] Global Systemd USE Flag Jason A. Donenfeld
2012-08-08 14:15 ` Michał Górny
2012-08-08 14:20 ` Jason A. Donenfeld
2012-08-08 14:36 ` Michał Górny
2012-08-08 14:38 ` Jason A. Donenfeld
2012-08-08 14:45 ` Michał Górny
2012-08-08 14:48 ` Jason A. Donenfeld
2012-08-08 15:14 ` Michał Górny
2012-08-08 15:20 ` Michael Mol
2012-08-08 14:47 ` Rich Freeman [this message]
2012-08-08 14:22 ` Jason A. Donenfeld
2012-08-08 14:33 ` Michał Górny
2012-08-08 14:35 ` Jason A. Donenfeld
2012-08-08 14:43 ` Michał Górny
2012-08-09 1:08 ` Walter Dnes
2012-08-08 14:48 ` Mart Raudsepp
2012-08-08 14:48 ` Patrick Lauer
2012-08-08 14:48 ` Jason A. Donenfeld
2012-08-08 14:53 ` Michał Górny
2012-08-09 8:48 ` Luca Barbato
2012-08-09 8:57 ` Michał Górny
2012-08-09 9:20 ` Luca Barbato
2012-08-09 10:01 ` Michał Górny
2012-08-09 11:22 ` Rich Freeman
2012-08-09 15:49 ` Luca Barbato
2012-08-09 11:58 ` Samuli Suominen
2012-08-08 15:03 ` Rich Freeman
2012-08-08 15:13 ` Michał Górny
2012-08-08 15:20 ` Rich Freeman
2012-08-08 15:25 ` Michał Górny
2012-08-08 14:31 ` Patrick Lauer
2012-08-08 14:32 ` Jason A. Donenfeld
2012-08-08 14:32 ` Michał Górny
2012-08-08 14:37 ` Richard Yao
2012-08-08 22:19 ` William Hubbs
2012-08-09 4:33 ` Jason A. Donenfeld
2012-08-09 6:57 ` [gentoo-dev] " Duncan
2012-08-09 7:24 ` Michał Górny
2012-08-09 10:24 ` Duncan
2012-08-09 12:29 ` Peter Stuge
2012-08-10 4:30 ` Duncan
2012-08-09 14:42 ` Ian Stakenvicius
2012-08-12 16:10 ` [gentoo-dev] " Jason A. Donenfeld
2012-08-13 8:53 ` Luca Barbato
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='CAGfcS_k3B59JoLW-PyjUQ7MrxxaCv=+FXzjGH6Th47AZ1vP1pQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
/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