-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 20 Sep 2010 06:46:21 -0400 "Anthony G. Basile" <bluen...@gentoo.org> wrote:
> Why can't we keep both? There are strong advantages/disadvantages > either way and there are users invested in both new/oldnet. I know > this is more work on doc writers, but I don't think that will equal > the pain users will experience being forced one way or another. 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. Worse yet, if BOTH are enabled, and we have to document both simultaneously. Then we'd have to fill up our docs with stupid conditionals: "IF you're using oldnet, use THIS complicated config, but IF you're using newnet, then follow THIS complicated set of steps." Documenting both config styles, whether simultaneously or sequentially, is massively complex, unnecessary, and a complete waste of time. I'd probably quit if I had to redo everything more than once, and then there would be absolutely no one to work on any docs. That's not a threat by the way, just a statement of likely outcome. I simply wouldn't have enough spare time to adjust the suddenly "broken" mass of documentation for the new config style. 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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAkyXnpYACgkQxPWMzpKk6kNdZwCgrVN6D12QzaHw5lXZl+h610PL /ccAni2xDC+CWwkTw9GKBCvjT/IDqcj9 =RxdN -----END PGP SIGNATURE-----
