public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up
Date: Mon, 02 Dec 2013 16:24:49 -0500	[thread overview]
Message-ID: <529CFAA1.7080608@gentoo.org> (raw)
In-Reply-To: <529CF973.2020008@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/12/13 04:19 PM, Rick "Zero_Chaos" Farina wrote:
> On 12/02/2013 03:28 PM, William Hubbs wrote: [...]
>> Also, the other message in this thread is correct; the netifrc
>> use flag is temporary.
> 
>> I originally planned to release openrc-0.12.x along with a
>> newsitem that instructed you to emerge the netifrc package if you
>> want the legacy network stack, but some users/devs felt that
>> Ishould go further to make sure netifrc remains installed on
>> their systems.
> 
> As one of those devs, I feel now may be a good time to ask.... What
> are we doing about this?  In my opinion, anyone removing net
> support from the stage3's should be killed with fire.  That said, I
> don't care if it's netifrc or whatever as long as it is properly
> documented and actually usable.
> 
> Thoughts on how we move forward?
> 
> Thanks, Zero
> 

Well, part of this conversation needs to be, what is the default
networking stack that we want to have in gentoo?  IMO that should
remain netifrc but that's just my personal opinion.

After deciding that, I expect we should decide how to include it.  My
guess would be, since for whatever reason we don't want netifrc as
part of @system or a dep of baselayout-2 or anything like that, we'd
need to add it to the special releng include list?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlKc+qEACgkQ2ugaI38ACPAu6AD/RpeD8NsMsjt4X5EKYe6Tkixu
6qzCONtd44U+grcxKr0BALw1EaxdI/EQ+Fo3eASssQ8fUH/dRFus5EUPo46dPz0L
=Bmfz
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-12-02 21:25 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 10:20 [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up Alessandro DE LAURENZIS
2013-12-01 10:36 ` Alexander V Vershilov
2013-12-02 20:28 ` William Hubbs
2013-12-02 21:19   ` Rick "Zero_Chaos" Farina
2013-12-02 21:24     ` Ian Stakenvicius [this message]
2013-12-03 17:32       ` Alexander V Vershilov
2013-12-03 21:11         ` William Hubbs
2013-12-03 21:43           ` Ian Stakenvicius
2013-12-03 23:00             ` William Hubbs
2013-12-03 23:29               ` Ian Stakenvicius
2013-12-04  1:14           ` mingdao
2013-12-04 15:57             ` William Hubbs
2013-12-04 16:46           ` Samuli Suominen
2013-12-04 21:25             ` William Hubbs
2013-12-04 21:30               ` Mike Gilbert
2013-12-04 22:31                 ` William Hubbs
2013-12-04 22:36                   ` Mike Gilbert
2013-12-04 23:42                     ` William Hubbs
2013-12-05 17:03                     ` Samuli Suominen
2013-12-05  8:01                   ` Martin Gysel
2013-12-05  9:23                     ` Steev Klimaszewski
2013-12-04 23:45                 ` Patrick Lauer
2013-12-05  0:13                   ` William Hubbs
2013-12-05  0:20                     ` Patrick Lauer
2013-12-05  0:17                   ` Mike Gilbert
2013-12-05  1:56                     ` William Hubbs
2013-12-06 15:26                       ` Ian Stakenvicius
2013-12-06 15:38                         ` Ben Kohler
2013-12-05  7:39                   ` Alan McKinnon
2013-12-05 12:30                     ` Rich Freeman
2013-12-05 17:01               ` Samuli Suominen
2013-12-07  5:52           ` Rick "Zero_Chaos" Farina
2013-12-07 12:42             ` Rich Freeman
2013-12-07 14:22               ` Rick "Zero_Chaos" Farina
2013-12-07 23:25                 ` Rich Freeman
2013-12-08  2:34                   ` Peter Stuge
2013-12-08 22:31                     ` William Hubbs
2013-12-14  6:22               ` Jorge Manuel B. S. Vicetto
2013-12-14 17:18               ` Jeroen Roovers
2013-12-07 15:04             ` Peter Stuge
2013-12-08 22:25             ` William Hubbs
2013-12-09 14:50               ` Rick "Zero_Chaos" Farina
2013-12-09 15:28                 ` Rich Freeman
2013-12-09 18:47                   ` Steev Klimaszewski
2013-12-09 19:56                   ` Rick "Zero_Chaos" Farina
2013-12-10  1:33                     ` Rich Freeman
2013-12-10 10:31                       ` Steev Klimaszewski
2013-12-10 11:23                         ` Rich Freeman
2013-12-10 18:46                           ` Steev Klimaszewski
2013-12-11 17:51                             ` [gentoo-dev] " Steven J. Long
2013-12-16 22:33                             ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-12-11  2:57                     ` William Hubbs
2013-12-14  5:56                       ` Jorge Manuel B. S. Vicetto
2013-12-14 20:13                         ` William Hubbs
2013-12-14 20:47                           ` Jorge Manuel B. S. Vicetto
2013-12-14 21:57                             ` William Hubbs
2013-12-14 22:22                               ` Luis Ressel
2013-12-16 22:38                               ` Rick "Zero_Chaos" Farina
2013-12-14 17:24                       ` mingdao
2013-12-15  0:59                         ` William Hubbs
2013-12-15  1:37                           ` mingdao
2013-12-16 22:41                           ` Rick "Zero_Chaos" Farina
2013-12-09 23:30                 ` Patrick Lauer

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=529CFAA1.7080608@gentoo.org \
    --to=axs@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