| 1 |
On Wed, 8 Aug 2012 16:20:55 +0200 |
| 2 |
"Jason A. Donenfeld" <Jason@×××××.com> wrote: |
| 3 |
|
| 4 |
> On Wed, Aug 8, 2012 at 4:15 PM, Michał Górny <mgorny@g.o> |
| 5 |
> wrote: |
| 6 |
> > INSTALL_MASK=/usr/lib/systemd |
| 7 |
> > |
| 8 |
> > And live happy to the day you notice your system no longer boots. |
| 9 |
> |
| 10 |
> This is a nice bandaid, and sure, it "solves" the immediate issue... |
| 11 |
> but it doesn't actually solve the actual issue: when packages |
| 12 |
> optionally install unwanted bloat, we make them an option via a USE |
| 13 |
> flag. In this case, especially, since systemd isn't even the default |
| 14 |
> (nor officially supported, whatever that amounts to), users certainly |
| 15 |
> should not have to manually add an install mask to make portage do |
| 16 |
> what it already should do. |
| 17 |
> |
| 18 |
> Besides, as systemd gains momentum, we can probably expect that |
| 19 |
> various pieces of software will have options to enable a systemd mode |
| 20 |
> or a systemd build, or what have you, and then in this case, a global |
| 21 |
> USE flag becomes even more imperative. |
| 22 |
|
| 23 |
The flag is there already, and it is used whenever it involves |
| 24 |
additional dependencies or in any other way makes the package |
| 25 |
incompatible with non-systemd systems. |
| 26 |
|
| 27 |
We aren't going to add USE flags which don't do anything. That topic |
| 28 |
was discussed a thousand times, and rising it once more won't change |
| 29 |
our decision. |
| 30 |
|
| 31 |
Similarly, bash-completion flag will be gone at some point. |
| 32 |
|
| 33 |
-- |
| 34 |
Best regards, |
| 35 |
Michał Górny |
Archives