All, the time has come when baselayout-2.x and openrc are stable on all of our architectures. That means that we should look into removing baselayout-1 from the tree, removing support for it from our init scripts and removing support for migration from the openrc ebuilds.
1. we can remove baselayout-1 from the tree, I think, as soon as bug #368597 is closed, because once that is done, all new installs should be based on baselayout-2.x and openrc. 2. The next step is to reverse the changes we made in bug #273138 and any other init scripts that have been reacting differently depending on whether they were under baselayout-1 or openrc. Optionally we could rework init scripts to take advantage of openrc specific features such as the *_pre/post functions at this point. Once this is completed, the init scripts in portage will not support baselayout-1, so if anyone is still on baselayout-1 we should find a way to encourage them to migrate -- maybe a news item? Also, we should come up with a time window that will be published in this news item that will mark the end of supporting migration from baselayout-1 to openrc. 3. The final step is to remove the code from the openrc ebuilds that supports migrating from baselayout-1.x. Once we do this another news item should be published since this is the point of no return; anyone running a baselayout-1 based system will have to re-install to upgrade once we drop this support. Please discuss. Did I leave out any steps? Are there any points I have left out besides the time window between steps 2 and 3? Should there be a time window before removing baselayout-1? What about between steps 1 and 2? What do you consider to be a reasonable time window before we stop supporting migration from baselayout-1 to baselayout-2/openrc? I'm thinking on the order of a few months, but not years. Thanks, William
pgpe1aEgTfPwn.pgp
Description: PGP signature
