| 1 |
On Wed, Apr 24, 2013 at 01:30:25PM -0500, William Hubbs wrote: |
| 2 |
> On Wed, Apr 24, 2013 at 02:16:51PM -0400, Rich Freeman wrote: |
| 3 |
> > On Wed, Apr 24, 2013 at 1:54 PM, William Hubbs <williamh@g.o> wrote: |
| 4 |
> > > if we keep a dependency for a while, even behind something like |
| 5 |
> > > IUSE="+oldnet", when we drop it, people will still be hit if they do |
| 6 |
> > > emerge --depclean before they emerge gentoo-oldnet. |
| 7 |
> > > |
| 8 |
> > > Also, (although I don't really care about this much because we tell people |
| 9 |
> > > not to do it), folks who set USE="-* foo bar bas" in their make.conf would |
| 10 |
> > > get hit immediately with this solution. |
| 11 |
> > > |
| 12 |
> > > Am I missing something? It just seems like this is putting off the |
| 13 |
> > > emerge command people will need to run for a while. |
| 14 |
|
| 15 |
I'm with the others: I don't think you ever want to 'drop' that default flag, |
| 16 |
at least not without equivalent functionality, which seems not to be provided |
| 17 |
by other methods at this point. An end-user can always turn it off, and people |
| 18 |
who use -* are supposed to know what they're doing. |
| 19 |
|
| 20 |
The name is troublesome given that we're discussing basic networking. |
| 21 |
|
| 22 |
> > It seems to me like network support needs to be some kind of default |
| 23 |
> > for Gentoo. A USE default is probably one of the least intrusive ways |
| 24 |
> > to do that - and we can always have an ewarn in the event both are |
| 25 |
> > suppressed (those who override all USE defaults should be on the |
| 26 |
> > lookout for trouble). |
| 27 |
> > |
| 28 |
> > Considering our default configuration ships sshd (an argument we don't |
| 29 |
> > need to rehash here), it seems a bit silly to not ship networking |
| 30 |
> > support by default. I'd rather not do it as part of the system set, |
| 31 |
> > though that would be consistent with what we're doing with ssh, and it |
| 32 |
> > is still override-able. |
| 33 |
> |
| 34 |
> If we did this as part of @system, it would have to be a virtual imo, |
| 35 |
> since there are several things in the tree that can manage networks |
| 36 |
> (openrc[newnet], dhcpcd, wicd, nm, etc), but this is a topic for another |
| 37 |
> thread. |
| 38 |
> |
| 39 |
> For OpenRC-0.12, I will put in the +oldnet use flag as suggested |
| 40 |
> previously if we go ahead with the split. |
| 41 |
|
| 42 |
Thanks, that sounds reasonable: one minor nitpick, though. Could you not |
| 43 |
call it 'stdnet'? Since from all the other discussion it appears like this |
| 44 |
is not going away soon for the vast majority of users, but simply being |
| 45 |
maintained as another package, which makes sense. And it is the standard Gentoo |
| 46 |
networking setup. |
| 47 |
|
| 48 |
That way, 'newnet' is clearly a more modern variant, but no-one's disparaging |
| 49 |
the traditional setup, which is after all, still the default. |
| 50 |
|
| 51 |
Regards, |
| 52 |
steveL. |
| 53 |
-- |
| 54 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |
Archives