1 |
On N, 1970-01-01 at 00:00 +0000, Jason A. Donenfeld wrote: |
2 |
> On Wed, Aug 8, 2012 at 4:33 PM, Michał Górny <mgorny@g.o> wrote: |
3 |
> > You are right. In case users really intend to use that, they may be |
4 |
> > better using app-portage/install-mask, and: |
5 |
> > |
6 |
> > $ install-mask -a systemd |
7 |
> > |
8 |
> > which will add just the right path. |
9 |
> |
10 |
> Still misses the point. USE flags were invented to deal with these |
11 |
> options. On a default install, which uses OpenRC, users shouldn't have |
12 |
> to then emerge an additional program to add more configuration in |
13 |
> order to have a clean system. |
14 |
|
15 |
USE flags are not meant for controlling every little thing, such as |
16 |
conditional installing a 400 byte file that does no harm when not used, |
17 |
other than taking 1 block of filesystem space (4kB or so), which can be |
18 |
workarounded by INSTALL_MASK if you are building an embedded system. I |
19 |
seriously doubt they were invented for such a purpose, but rather to |
20 |
control ./configure arguments and external dependencies. |
21 |
|
22 |
No, wanting to get rid of those on a desktop/server via a USE flag (as |
23 |
opposed to an INSTALL_MASK) is not a consideration, as that's users |
24 |
completely unneeded desire for no technical reason. If taking 500kB |
25 |
total for systemd service files is an issue, then the issue really is |
26 |
that you are using a 1GB /usr partition or something. |
27 |
|
28 |
This all is similar to how we in GNOME unconditionally install user and |
29 |
developer documentation, as long as it does not impose any extra build |
30 |
time or downloads. |
31 |
(no, this is not really negotiable for change, and we are talking about |
32 |
more than 400 byte files here; we'd be happy however if portage binary |
33 |
packages supported splitting of the source packages files to separate |
34 |
packages, so that binary distribution derivatives could work in a |
35 |
similar model as purely binary distributions) |
36 |
|
37 |
USE flags typically control the functionality of compiled binaries, |
38 |
usually involving external dependencies to achieve such extra |
39 |
functionality. |
40 |
|
41 |
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2#doc_chap1_sect2 |
42 |
|
43 |
|
44 |
Best Regards, |
45 |
Mart Raudsepp |