public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich@thefreemanclan.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Opinions Wanted - Arrays again :)
Date: Fri, 26 Oct 2007 23:02:04 -0400	[thread overview]
Message-ID: <4722AA2C.9080306@thefreemanclan.net> (raw)
In-Reply-To: <1193433447.3487.11.camel@uberpc.marples.name>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roy Marples wrote:
> One issue with that is there is no automatic way of doing that. We just
> pass the array elements onto the various programs
> 
> config_eth0=( "1.2.3.4/24" "some voodoo" )
> becomes
> ifconfig eth0 1.2.3.4/24
> ifconfig eth0 some voodoo
> 
> We also do the same for iproute2 which has a very comples language
> structure. We also do this for most of the helper programs that we use -
> vlan, bridging, wireless just to name a few.
> 
> Do we want variables for every single possibility?
> 
> The beauty with the array structure is that it allows the user to define
> a sequence of commands to send to a helper. The issue with the array
> structure is that it is bash and we strive to support non bash shells
> hence the discussion.
> 

Thanks for clarifying this - I can see the where you're coming from a
bit better in light of this explanation.  I think that as long as the
documentation is clear and well-commented we should be in good shape -
the goal is of course to make things fairly transparent to the
less-educated among us - especially when we're talking about something
simple like setting up a static IP network or DHCP.  At the same time,
if we can accomplish that while also allowing for folks using
multi-homed systems with all kinds of bridges and cost-based routing and
all that so much the better...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHIqooG4/rWKZmVWkRAlo2AKCmJy98UKFngz/PuHQwbJ9X4LKsxACgo+TS
Ze5HKc9YgqvIJr9Y29gSn5E=
=WPAf
-----END PGP SIGNATURE-----

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 4101 bytes --]

  reply	other threads:[~2007-10-27  3:05 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
2007-10-26 18:57                 ` Duncan
2007-10-26 21:17                   ` Roy Marples
2007-10-27  3:02                     ` Richard Freeman [this message]
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=4722AA2C.9080306@thefreemanclan.net \
    --to=rich@thefreemanclan.net \
    --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