Thomas Trepl wrote: > I would like to make a citation of your mail regarding the bootscript changes > and add it to the Editors Guide. > >> When you make an update to the bootscripts there are three things >> that need to be done: >> >> 1. The actual update to the bootscript(s). >> 2. Update the ChangeLog file in the bootscripts. Note that there is >> a separate changelog for the bootscripts. The actual book changelog >> doesn't need an update. >> 3. Update the "blfs-bootscripts-version" entity in the book's >> general.ent file. >> >> If you fail to do #3, then the automated process which creates a new >> version of the bootscripts tarball won't do its job, so #3 is an >> important step in the process. > > This is the section i would like to take - I prepared a patch (you have it as > an attachment) onto the edguide. Please let me know whether you feel > comfortable with it or when I should better take the hands off. In the first > case, I'd commit that to svn. ...or let me know any further suggestions! > >> (Note that I will update general.ent today to account for the recent >> changes put in by Thomas) > Never thought that this tiny 't' I added there causes so much actions...
Actually, it's good that it all happened as there was a learning experience. And yes, your commit looks great. Additionally in #1, not only would you edit the bootscripts to "enhance the functionality or fix bugs", but it could be that you needed to *add* a new bootscript for a new package or whatever. Feel free to commit the changes. And try to keep these types of discussions on -dev (I cc'd this message). If you needed a bit of help, you're probably not the only new dev that didn't know it either. Good job, Thomas. And thanks for doing it. -- Randy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
