Jim Gifford wrote these words on 01/09/06 10:52 CST: > I just saw the page in DJ's directory, that's what through me off.
I do not care for the instructions either. *Way* too automated. We may as well just make a tarball of all the packages, host it and a script that does everything. That way, folks wouldn't even have to read the instructions. Just download the two files and type "go". :-) Seriously, though, why so much automation? Can't we leave it to the readers to automate how they wish? Why are we putting instructions in to create log files? Other than the GCC instructions, where it is critical that one doesn't do "make install" until he is confident that all is good, we don't even *mention* log files in *any* package instructions? Now, we're providing it. Why? I think we should specify the packages and give a build order, and leave it to readers to figure out how *they* want to do it. If folks want to create hints for more automation, great, but right now I think the instructions are too automated. Just an opinion. -- 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] 11:02:00 up 106 days, 20:26, 3 users, load average: 0.87, 0.37, 0.18 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
