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