public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Marples <uberlord@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Opinions Wanted - Arrays again :)
Date: Fri, 26 Oct 2007 18:03:03 +0100	[thread overview]
Message-ID: <1193418183.3487.3.camel@uberpc.marples.name> (raw)
In-Reply-To: <pan.2007.10.26.16.36.06@cox.net>

On Fri, 2007-10-26 at 16:36 +0000, Duncan wrote:
> Well, several services already have a "basic" setup using named vars, 
> then something like Richard's suggested Options_eth0= as a (normally 
> commented) catch-all for anything advanced that the admin wishes to pass 
> "raw".  IMO the standard network stuff is well defined enough for that, 
> perhaps with a couple of mode-toggles and/or counters thrown in.  (A 
> counter like eth0_number_IPs= could default to one, for instance, but set 
> to something higher and with the appropriate number of address_N_eth0= 
> lines, it'd then cover your 5-address example, without having to worry 
> about figuring out how many there are, since it's a given.)
> 
> I think that's what many of us would like and what this subthread is 
> asking for, truth be told, but I also realize it's going to be more work 
> setting it up -- but OTOH should be simpler for the user to setup so 
> perhaps less bugs to deal with and the documentation in the net sample 
> file should be somewhat simpler as well.  The more work thing is why I've 
> not requested it before, but it'd be nice, and with others mentioning it 
> now too, now's the time to speak up if I'm going to. =8^)

Fair enough, but one of the goals of baselayout-2 is to support
baselayout-1 configs where possible if the shell is still bash.

I'm striving to support similar configs for non bash shells so that
there's not much of a learning curve.

Yes we could have a totally new non compatible setup, but that would
really suck hard for upgraders yes?

Thanks

Roy

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-10-26 17:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 15:40 [gentoo-dev] Opinions Wanted - Arrays again :) Roy Marples
2007-10-25 16:02 ` Marijn Schouten (hkBst)
2007-10-25 16:18   ` Roy Marples
2007-10-25 16:37     ` Ioannis Aslanidis
2007-10-26 11:30     ` Roy Marples
2007-10-25 17:18 ` Josh Saddler
2007-10-25 21:31 ` Donnie Berkholz
2007-10-25 21:49   ` Roy Marples
2007-10-25 22:56     ` Donnie Berkholz
2007-10-26  6:28       ` Roy Marples
2007-10-26 10:16         ` Richard Freeman
2007-10-26 10:42           ` Roy Marples
2007-10-26 16:36             ` [gentoo-dev] " Duncan
2007-10-26 17:03               ` Roy Marples [this message]
2007-10-26 18:57                 ` Duncan
2007-10-26 21:17                   ` Roy Marples
2007-10-27  3:02                     ` Richard Freeman
2007-10-28  6:46                 ` [gentoo-dev] " Steve Long
2007-10-29  7:35                   ` Natanael Copa
2007-10-30  3:55                     ` [gentoo-dev] " Steve Long
2007-10-26  6:13 ` [gentoo-dev] " Alec Warner
2007-10-26  6:32   ` Roy Marples
2007-10-29  9:50 ` Roy Marples
2007-10-30  3:58   ` [gentoo-dev] " Steve Long

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=1193418183.3487.3.camel@uberpc.marples.name \
    --to=uberlord@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