public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: oldnet scripts splitting out from OpenRC
Date: Wed, 24 Apr 2013 14:46:43 -0400	[thread overview]
Message-ID: <201304241446.44543.vapier@gentoo.org> (raw)
In-Reply-To: <20130424175407.GA2404@linux1>

[-- Attachment #1: Type: Text/Plain, Size: 2237 bytes --]

On Wednesday 24 April 2013 13:54:07 William Hubbs wrote:
> On Wed, Apr 24, 2013 at 01:34:36PM -0400, Mike Frysinger wrote:
> > On Wednesday 24 April 2013 13:23:23 William Hubbs wrote:
> > >  The issue is that OpenRC does not have any kind of dependency on
> > >  gentoo-oldnet at all. There will be a separate loopback script in
> > >  OpenRC so it is possible to run OpenRC on a system without the oldnet
> > >  or newnet scripts. In fact, this is a completely valid configuration.
> > > 
> > > OpenRC doesn't "link" to gentoo-oldnet in any way, so there is no
> > > dependency.
> > > 
> > > The way I read the dev manual [1], a newsitem and postinst messages are
> > > the way to go for somethinglike this.
> > 
> > it is reasonable to expect openrc updates to *not* break a system.  that
> > means people shouldn't be required to read a news/postinst message to
> > keep from killing things.
> > 
> > even then, a default Gentoo system should have networking support
> > available by default.  our manuals assume this, and people shouldn't
> > have to install a stage3 and then do `emerge gentoo-oldnet` just to have
> > that happen.  so keeping a dependency in openrc (perhaps initially hard,
> > or behind IUSE=+oldnet) makes sense.
> 
> I was planning on opening a bug before all of this hit stable to have
> releng add gentoo-oldnet to the stages when it does hit stable.

"adding to the stages" isn't a magic incantation :).  it's either part of 
@system, or it's a dependency in a package that is part of @system.  i don't 
think adding it straight to @system makes sense, and i don't think there's 
really an existing dependency other than openrc where this would be 
appropriate.

> if we keep a dependency for a while, even behind something like
> IUSE="+oldnet", when we drop it, people will still be hit if they do
> emerge --depclean before they emerge gentoo-oldnet.

i don't think we should drop it.  openrc is logically the best place imo.

i understand your position that openrc works just fine w/out these scripts.  
but i don't think that pure logical distinction is really necessary here.  if 
people really truly don't want it, they have a USE flag to turn it off.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-04-24 18:46 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 16:16 [gentoo-dev] rfc: oldnet scripts splitting out from OpenRC William Hubbs
2013-04-24 16:45 ` Diego Elio Pettenò
2013-04-24 17:01   ` William Hubbs
2013-04-24 17:30     ` Mike Frysinger
2013-04-24 21:00     ` Diego Elio Pettenò
2013-04-24 16:58 ` Ian Stakenvicius
2013-04-24 17:23   ` William Hubbs
2013-04-24 17:34     ` Mike Frysinger
2013-04-24 17:54       ` William Hubbs
2013-04-24 18:16         ` Rich Freeman
2013-04-24 18:30           ` William Hubbs
2013-04-25 21:01             ` [gentoo-dev] " Steven J. Long
2013-04-26  8:41               ` Tobias Klausmann
2013-04-26  8:58                 ` Tobias Klausmann
2013-04-26 11:20                   ` Michael Mol
2013-04-26 16:24                     ` »Q«
2013-04-24 22:34           ` [gentoo-dev] " Walter Dnes
2013-04-24 23:17             ` William Hubbs
2013-04-24 23:32               ` Rick "Zero_Chaos" Farina
2013-04-25  0:05                 ` Carlos Silva
2013-04-25  1:10                 ` William Hubbs
2013-04-25  1:39                   ` Ian Stakenvicius
2013-04-25  2:12                     ` Zac Medico
2013-04-25 18:10               ` Mike Frysinger
2013-04-25 18:27                 ` G.Wolfe Woodbury
2013-04-25 18:54                   ` Rich Freeman
2013-04-25 19:08                   ` Mike Frysinger
2013-04-24 18:46         ` Mike Frysinger [this message]
2013-04-24 22:18           ` Patrick McLean
2013-04-26 17:27         ` Chí-Thanh Christopher Nguyễn
2013-04-26 18:12           ` Robin H. Johnson
2013-04-26 18:14             ` Ian Stakenvicius
2013-04-26 18:53               ` William Hubbs
2013-04-25  3:13       ` Alec Warner
2013-04-25  3:32         ` William Hubbs
2013-04-24 19:00 ` Michał Górny
2013-04-24 19:17   ` William Hubbs
2013-04-25 19:09     ` vivo75
2013-04-25 23:07       ` Mike Frysinger
2013-04-26  8:44     ` Tobias Klausmann
2013-04-25 16:50 ` Vadim A. Misbakh-Soloviov
2013-04-25 16:58   ` Rich Freeman
2013-04-25 17:13     ` Carlos Silva
2013-04-25 17:17       ` Peter Stuge
2013-04-25 17:18         ` Carlos Silva
2013-04-25 17:23           ` Peter Stuge
2013-04-25 17:23       ` Tom Wijsman
2013-04-25 22:15       ` [gentoo-dev] " Duncan
2013-04-25 22:51         ` Carlos Silva
2013-04-25 23:12           ` Peter Stuge
2013-04-25 23:15           ` Ambroz Bizjak
2013-04-26  8:37           ` Duncan
2013-04-25 23:49 ` [gentoo-dev] OldNet out of OpenRC: as the requester Robin H. Johnson
2013-04-26 10:13   ` Alexander Berntsen
2013-04-26 14:14 ` [gentoo-dev] rfc: oldnet scripts splitting out from OpenRC Luca Barbato

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=201304241446.44543.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