On Sat, 2007-07-21 at 11:48 -0700, Josh Saddler wrote: > (GDP): you give us the info, we'll document it for you. Or I will at least.
Well, the changes are as outlined in my first email. The user changes are mainly a few variables in the /etc/conf.d/* files that baselayout ships. For example a few have been removed and a few have been added, and a few have changed. >From our perspective, /etc/conf.d/* is quite well documented, so GDP could easily diff the files to see what has changed. > Of equal concern to me, however are a few issues: > > 1) How will stabilization work? Is it a forced upgrade from stable 1.x > to 2.x, or can it be slotted? It cannot be slotted in any way or form. Also, the daemon state data is non transferable as the format has changed in baselayout-2. This is the data that records how a daemon was started by s-s-d so we can check if it's running or not. However, most end users won't be concerned by this. I've tested the ebuilds for upgrading and downgrading quite extensively, with the following notes. baselayout-1 *requires* bash. As such /bin/sh should point to bash before downgrading. If the /etc/init.d files are not immediately updated by etc-update or other means then errors will happen. What errors and how severe entirely depend on the scripts the user has in /etc/init.d > 2) It will be completely unmanageable to have more than one set of > baselayout instructions in the handbook & other docs, so there > definitely is a need for the migration doc. That's your call. > 3) How long will 1.x be kept stable? (This affects how long the old > instructions are in the handbooks etc.) Good question. We normally keep at least one major revision prior to the current stable in the tree. They can stay in the tree indefinitely I suppose, but the GDP should only follow the current stable. Maybe archive the handbook? > 4) What baselayout will be used in the next release? (Maybe that's more > of a releng question.) baselayout team just makes baselayout releases. If you mean the LiveCD then ask releng. > 5) Do you have a rough estimate (month, 3 weeks, 5 weeks, what?) on when > the first arches might be stabilizing 2.x? No. If the RC's prove stable and no serious regressions are reported for a month then we'll probably release a final 2.0.0 and get arch teams to mark stable a week later, or right away if no last minute changes have been made. > This is all from the GDP's perspective, almost none of it is of interest > to me as a user; I expect this sh** to work just as well as > baselayout-1.x when I hit the upgrade myself. :) In theory it should just work. Especially as Gentoo/FreeBSD has been running it as our standard baselayout for around 6 months now. So hopefully this should be a very smooth release. > Documenting this will be a major arsepain--er, effort--since baselayout > 1.x directions are already mixed in so well with pretty much every doc > we have. I'm not at all looking forward to fixing the docs when the time > comes, but I will do it provided I get to borrow your brain for a good > long time. :) Most of the documentation should still apply. I've tried to be as compatible as possible - the one possible exception being networking as baselayout-1 used bash arrays extensively. But we still support that if /bin/sh is bash, which it is by default for Gentoo/Linux Thanks Roy -- [EMAIL PROTECTED] mailing list
