On Wed, 07 Feb 2007 09:47:33 -0500 Patrick McLean <[EMAIL PROTECTED]> wrote:
> So this means that you are planning to stop development of the > current baselayout in favor of baselayout-ng? No. baselayout will get all the nice features that baselayout-ng will get, except that it will force bash to match the documentation. > > > > > We still need something that is "array like" for want of a better > > phrase, so how about delimiting using ; like so > > config_eth0="10.1.1.1 netmask 255.255.255.0; 10.1.1.2/24" > > > > Couldn't you use the current config on bash shells and parse it to > something like that on non-bash. There is no reason why the shell > needs to source the config file, it could be parsed just as easily, > and writing the parser shouldn't be too hard with a bit of sed magic. Not being rude or anything, but what does it take to get this into peoples mindlessly thick skulls? THE CONFIG FILE HAS TO BE PARSEABLE BY ANY SHELL or EVERY SHELL HAS TO BE PATCHED TO UNDERSTAND BASH ARRAYS Simply put, this has to work where /bin/sh is any valid POSIX shell. #!/bin/sh . /etc/conf.d/net The third alternative is that we drop baselayout and use upstart, init-ng, einit, runit, or something else which will require more than just a change to /etc/conf.d/net Thanks Roy -- [email protected] mailing list
