Ok, so we have a fair amount of items we'd like to push into 7.0, some of which, work has already begun.
As far as step-by-step plan of attack goes, how does this sound? 1. Move to DIY's new build method in trunk. If we ignore multilib and any extra arch support for this step, the changes required aren't actually that many, and they all take place pretty early in chapter 5. We can have trunk using the new build method within a day. 2. Add instructions for DESTDIR commands. I don't think there has yet been a consensus yet on what type of PM to use. But, if we make the instructions just slightly more PM friendly by adding in DESTDIR commands it opens up a wide range of possibilities. If we limit the changes now to just adding in DESTDIR commands and a short explanation about what these mean somewhere or how to work with them, we should be able to drop this into trunk in a short time (a day or two?). Otherwise we may need a separate branch for PM. 3. Merge all recent changes in trunk to the jh branch, copy that branch to a new multi-arch branch and strip out anything extra that doesn't really have to do with adding multiple archs. (I don't think there are many, but I'd just have to do a quick look.) Hopefully making this its own branch again would encourage a few more people to get involved in finsihing up these changes. If desired, multilib support could also be added to this branch. 4. Ticket 2284, upgrade of Udev, and strip out udev-config. I doubt this needs its own branch. What sort of time/work is involved here? 5. Ticket 2033. Include support for initramfs. Would this require a separate branch, and can it be worked on in parallel to other changes, or is it better to wait until other above changes are sorted out? Have I missed anything? -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
