Jim Gifford wrote these words on 05/23/06 16:07 CST:
What everyone wants is a unified package, where all the scripts for BLFS, CLFS, and LFS are in one package. We will need to become dependent on the this team that will be handling this package. We can have them release a nightly tarball if we need to, but these are the details that all the leaders will need to provide to this team once it's conceived.
Then that unified package should be automated just like the BLFS bootscripts are done. Jim it has to be this way. I remember when you quit the project for a month, and Tushar wasn't around. BLFS waited *weeks* to get patches available. *Weeks*. At that point we forked the patches project and went on our own. We had to. There was no choice. Let's figure out some method so that the tarballs are auto generated like the BLFS bootscripts are now. Each team has their own repo, and updates it. If at nightly rendering the script sees there's been changes, then a new unified tarball is created. Why do we have to have release managers for bootscripts? That is ridiculous. If there's been changes, make a new tarball, simple as that. I think unified tarballs are a great idea. It seems ridiculous to me that an editor cannot update a bootscript (or add one) to his team's book. What is gained? If an editor isn't allowed to update bootscripts for his book, that would be no different than moderating the actual SVN files for the books. All editors need privileges to see that their changes are available. Why the moderation? -- Randy rmlinux: [bogomips 3995.17] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.16.14 i686] 16:11:00 up 2 days, 6:21, 8 users, load average: 0.07, 0.06, 0.01 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
