-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi William.
On 12-05-2011 14:34, William Hubbs wrote: > Hi Jorge, > > On Thu, May 12, 2011 at 02:01:19AM +0000, Jorge Manuel B. S. Vicetto wrote: >> On 12-05-2011 01:45, William Hubbs wrote: >>> In my opinion, the best way to fix this, and the best way forward, would >>> be to stop doing this. My plan is something like this: >>> >>> For the next openrc release, put in a warning that config_* is >>> deprecated and advise the use of ifconfig_* or ipconfig_* depending on >>> which interface handler is being used. Then, at some point in the >>> future, remove support for config_*. >>> >>> Does anyone have any thoughts? >> >> William, >> >> isn't that the whole point of the "modules" variable in the config file? >> One of the first things I do when configuring a new system is to edit >> /etc/conf.d/net and I start by adding modules="iproute2" to it. > > I'm not sure I follow. would you rather keep the config_* variable? I think we should try to keep them. > If so, how do you feel about requiring the syntax of the variable to > match the tool you are using? > That would mean that the following snippets would not work: > > modules="iproute2" > config_iface="x.x.x.x netmask y.y.y.y broadcast z.z.z.z" > # the above is using ifconfig syntax with the iproute2 module > > modules="ifconfig" > config_iface="x.x.x.x/y broadcast z.z.z.z" > # This is using iproute2 syntax with the ifconfig module. That's exactly what I meant. By choosing the module one would get tied to its syntax. That should make it simpler to parse the data. I would also suggest making the declaration of modules mandatory or for you to pick a default tool to be used when someone doesn't declare modules. I prefer iproute2 syntax, but I suspect most people would prefer ifconfig. As long as I have an option to use iproute2, I don't have a problem :) > William - -- Regards, Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNzHICAAoJEC8ZTXQF1qEP6qUQAMeBWdnItCG2IyQDcUfeDVh0 F6rbngiYPu/AETXvyBfcx0d0rmaszqrqQLWGoNEZVJlPIbHTGD3kTrBVYatTAsIb ooDAcDa3G7yjc/NLu3FRXmJv7Ed+qNFOm9/jDCRH+bOS69rD23BoR0KiRhriFGg8 OwsNxyrFyvRFmoZH1CBfbOcXMlEUBP401iiaeGs+2zuSwFZErRWVIvUQcgaf8evI 6zYk4Lxyh/OHVHhBiumDrJ3izhZklBAVQnYvxvId+kbhvxKPLgI3sZjDZx/L1Qd5 oA7UaLJu+7qFfesj4UXH+VLj0uxIWl398Ka9ZU9h6H08MNde8l6N3rn2D+wkoMax h5mSsWQiRKRqdUIS3vGddLJyd29LNhrixY7FRKnSnSJMgDpxcb25CYU66zJXga3I dO4Fta9e4qdFtZwfsiTxuFAd4XVWrZ2+HkgIthULCXfk92bSgHxU2sdzkBlVju2U 1prywa79wK/hm5Y7miAaRbVkJ2iI/DI/46rphnny/JLDsbcD+M37xbG2Ypw6/Jt7 jmpuHs+Vu2PyFaAA84q/pBPQFJBckReyB0+8l+RDV15zPy4gPdc1nqj4HDhFAj27 SFBKjpYbGJ7VFW0vjZGO5k8E4z3Ecn/X2QlBtlPFrk3Nxk2EG6yTC7H0Q5/i+Pam 3DNpqx0iGmLIWixmjHyJ =gDFf -----END PGP SIGNATURE-----
