-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/20/2010 02:32 PM, Mike Frysinger wrote: > On Monday, September 20, 2010 13:49:08 Joshua Saddler wrote: >> Wrong. It will. The GDP--that's effectively just me--will already have to >> rewrite every single one of hundreds of pages of documentation to allow >> for the new syntax and way of doing things present in the "oldnet" >> behavior of OpenRC. That's ~weeks to ~months of work, even if there's >> someone besides me doing it. I'll have to do all that effort and time >> commitment yet again if we have to rewrite everything once "newnet" >> becomes the default after everyone uses "oldnet" for a while. > > man, fix your line length. what a nub you are. > >> Please. Just stick to *one* config. I strongly suggest that it be "oldnet," >> given all the problems with "newnet" raised in this thread. But more >> importantly, because *the groundork has already been done* when I wrote >> the OpenRC Migration Guide. I can piggyback all my efforts off that guide, >> which will greatly shorten the amount of time needed for the rest of the >> documentation. Otherwise a completely new "migration" guide will have to >> be written, AND all the docs will need to be adjusted to THAT one. > > we're going with oldnet by default in stable and that'll be what the GDP has > to worry about. newnet will still be there, but people will have to manually > opt out of oldnet and opt in to newnet. i dont think we need to worry about > documenting it in the handbook for now ... the bundled files with openrc are > sufficient. > -mike
+1 I'm not even worried about documenting newnet. I just don't want it thrown out of openrc. Leaving it in the background is fine. - -- Anthony G. Basile, Ph.D. Gentoo Developer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyX8GMACgkQl5yvQNBFVTUFZgCdGbk0Irx9VJUJqnGDcGjlSOcr 6sIAn2zaKI7gNa1q9qfyYzZgwX11a8/T =r/Iw -----END PGP SIGNATURE-----
