Bruce Dubbs wrote these words on 12/16/05 10:18 CST: > Here are the options as I see them: > > 1. Remove the yes construct completely. > 2. Make the packages conform to the method of freetts. > 2a. Promote the explanation of 2 to an <important> section right before > the actual script. > 3. Explain the method in a <note> without putting it actually in the > <screen> section.
My preference is #1 because this is the safest thing legal-wise, and it is my opinion that if someone needs to script their build, they probably know how to do it without being told how. I have many non-BLFS packages that have automated scripting techniques incorporated into them. Some pipe 'yes', some pipe 'yes' but throw something other than 'yes' to the build, some install a configuration file by hand instead of going through the configuration setup script and I probably use other methods as well. The level of expected knowledge for LFS/BLFS readers should be high enough that they can figure out how to script their builds. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 10:24:00 up 82 days, 19:48, 3 users, load average: 0.08, 0.47, 0.64 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
