Jeremy Huntwork wrote: > Well, I don't mind working from trunk until such time as we feel we are > ready for a release candidate. Then we tag it, build, and release. If no > bugs are found in say, a week?, we move the release candidate to the > stable CD on the main mirror and let the others sync. (Main mirror > configuration being updated, will provide more info in the near future.) > If we find a bug somewhere, we copy the tag to a branch, update it, tag > it anew, build and release again. > > At least, this is how I picture the flow. Comments/suggestions welcome. > My objection is based on the feeling that x86 and x86_64 CDs will not become ready simultaneously. If you disagree, please ignore me and remove linux64 from what will become the 6.3 release.
Also, do I understand correctly that we will release 4 CDs in the 6.3 release announcement: x86 full, x86_64 full, x86 minimal and x86_64 minimal? How are you going to deal with the fact that there is no official LFS-6.3 for x86_64? Maybe it is a good idea to stop calling x86_64 CDs "6.3"? > As far as being able to build x86_64 CLFS, to me, that's up to the > community. I could very well be wrong, but I don't get the feeling that > there's many CLFS users that make use of the CD. And if they do, do they > need to be able to chroot? Yes, that's why I added a 64-bit kernel. The "boot" method makes the machine unusable for normal work while building through their equivalent of Chapter 6. Also, the CD is mentioned in the CLFS book. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/livecd FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
