Alexander E. Patrakov wrote: > OK - and maybe I will accept your original proposal after some > discussion of the following questions: "which branches are for the 6.3 > release and which are not", and whether it is a good idea to have a > "stable" CD that can build both 32-bit LFS and 64-bit CLFS.
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. 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? They have an entire section for setting up alternate boot methods. I'll go with whatever you prefer on this Alex, but I would like to hear something back from the CLFS community or developers. -- JH _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
