From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: should openrc be mandatory on all gentoo systems?
Date: Wed, 29 Jun 2011 23:47:42 -0400 [thread overview]
Message-ID: <201106292347.42829.vapier@gentoo.org> (raw)
In-Reply-To: <20110630041909.4e41e27b@pomiocik.lan>
[-- Attachment #1: Type: Text/Plain, Size: 1124 bytes --]
On Wednesday, June 29, 2011 22:19:09 Michał Górny wrote:
> On Wed, 29 Jun 2011 16:46:13 -0500 William Hubbs wrote:
> > Ok, the option that I'm looking at now is to set up openrc so that the
> > init scripts are optional and whether or not they are installed is
> > controlled by a use flag which I will default to on in IUSE. Most
> > people would leave this flag alone, but if you want to use something
> > like systemd and do not want the init scripts or the /etc/runlevels
> > directory on your system, you would just re-emerge
> > openrc with this flag disabled.
> >
> > For now this flag will just control init scripts installation, but I
> > will also look into taking it further and not installing other parts
> > of openrc, such as binaries, man pages, etc which are only used if
> > you are working on init scripts.
>
> Wouldn't it be better to just leave these people with INSTALL_MASK?
> USEflag means needless rebuilds just for the benefit of one file.
so you're saying the solution for systemd users is to setup INSTALL_MASK and
we shouldnt worry about tweaking openrc at all ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-06-30 3:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 22:10 [gentoo-dev] rfc: should openrc be mandatory on all gentoo systems? William Hubbs
2011-06-29 1:07 ` Olivier Crête
2011-06-29 2:12 ` William Hubbs
2011-06-29 6:39 ` Mike Frysinger
2011-06-29 9:08 ` Patrick Lauer
2011-06-29 10:49 ` Anthony G. Basile
2011-06-29 11:48 ` Rich Freeman
2011-06-29 15:14 ` Olivier Crête
2011-06-29 15:31 ` Patrick Lauer
2011-06-29 15:40 ` Jeremy Olexa
2011-06-29 15:46 ` Ciaran McCreesh
2011-06-30 0:26 ` Nirbheek Chauhan
2011-06-30 1:02 ` Olivier Crête
2011-06-30 1:11 ` Rich Freeman
2011-06-29 4:04 ` Michał Górny
2011-06-29 5:05 ` Mike Frysinger
2011-06-29 5:48 ` Nirbheek Chauhan
2011-06-29 6:07 ` Mike Frysinger
2011-06-29 6:12 ` Nirbheek Chauhan
2011-06-29 6:35 ` Mike Frysinger
2011-06-29 6:41 ` Matt Turner
2011-06-29 6:48 ` Mike Frysinger
2011-06-29 6:14 ` Ciaran McCreesh
2011-06-29 6:36 ` Mike Frysinger
2011-06-29 6:38 ` Ciaran McCreesh
2011-06-29 6:47 ` Mike Frysinger
2011-06-29 6:53 ` Ciaran McCreesh
2011-06-29 7:36 ` Mike Frysinger
2011-06-29 11:49 ` Peter Volkov
2011-06-29 13:46 ` William Hubbs
2011-06-29 7:38 ` Ulrich Mueller
2011-06-29 17:01 ` Mike Frysinger
2011-06-29 10:05 ` Michał Górny
2011-06-29 17:09 ` Mike Frysinger
2011-06-29 14:57 ` William Hubbs
2011-06-29 16:56 ` Mike Frysinger
2011-06-29 21:46 ` William Hubbs
2011-06-30 2:19 ` Michał Górny
2011-06-30 3:47 ` Mike Frysinger [this message]
2011-06-30 12:58 ` Paul de Vrieze
2011-06-30 15:04 ` Mike Frysinger
2011-06-30 16:14 ` Rich Freeman
2011-06-30 17:12 ` William Hubbs
2011-06-30 21:14 ` Michał Górny
2011-06-30 21:16 ` Mike Frysinger
2011-06-30 21:30 ` Michał Górny
2011-06-30 21:49 ` William Hubbs
2011-06-30 22:18 ` Mike Frysinger
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=201106292347.42829.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.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