Dan Nicholson wrote these words on 02/10/07 13:07 CST: > I'm ripping off one more build right now before I commit it. The > command will bomb on some of the drivers because the don't have > "man/*.man" files. Do you think this is an issue? They're defintely > there for the packages I mentioned in the diff. The other option is to > add some conditionals around the sed to check that the files exist.
I'm against anything that could disrupt scripting (one of many packages fail, and someone may not be doing proper error checking - Yes, I agree that if they follow the book, errors should be caught). So, to rephrase, I'd like us to keep the book sane enough so that if someone doesn't do error-trapping, *we* don't throw something into the mix that breaks things. Now, that said (and I should reread your original post), as long is it is identified which packages need the seds, then that should be fine. And IIRC, you do mention them, so everything is fine. For me, as long as I know beforehand which packages need special care, then it is up to me to take care of it. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 13:10:00 up 31 days, 13:24, 1 user, load average: 0.59, 0.23, 0.13 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
