| 1 |
On 31/07/13 at 11:26am, Tanstaafl wrote: |
| 2 |
> On 2013-07-31 11:20 AM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 3 |
> > If you don't use the systemd USE flag (and never install anything that |
| 4 |
> > depends on systemd), you will not get systemd installed, but many |
| 5 |
> > packages will install systemd unit files in /urs/lib/systemd/system. |
| 6 |
> > This unit files are little non-executable files which do nothing in |
| 7 |
> > your system, but some people feel really strongly about having |
| 8 |
> > anything in their machines with *systemd* in its path. If you want to |
| 9 |
> > exorcise those unit files, add /usr/lib/systemd/system to |
| 10 |
> > INSTALL_MASK. |
| 11 |
> |
| 12 |
> Ok, thanks Canek... but my last question remains... if this really is |
| 13 |
> going to be the only and one true way to opt out of systemd, shouldn't |
| 14 |
> this be well documented in the man page, as opposed to just generic |
| 15 |
> references to masking 'files'...? |
| 16 |
|
| 17 |
The "one true way" is to set -systemd in your useflags. However anything |
| 18 |
that hard depends on systemd will pull it in like AFAIR gnome. Trying to |
| 19 |
opt-out of systemd in these cases is not supported and probably not |
| 20 |
trivial. |
| 21 |
|
| 22 |
The install_mask is just for preventing certain tiny files that certain |
| 23 |
packages install that let them be used by a init sytstem like the |
| 24 |
scripts in init.d in the case of openrc and unit files in the case of |
| 25 |
systemd. ALl this will do is help you save few kbs of disk space. It |
| 26 |
wont help you get rid of systemd in cases where its required like in the |
| 27 |
case of gnome. |
| 28 |
|
| 29 |
-- |
| 30 |
|
| 31 |
- Yohan Pereira |
| 32 |
|
| 33 |
The difference between a Miracle and a Fact is exactly the difference |
| 34 |
between a mermaid and a seal. |
| 35 |
-- Mark Twain |
Archives