On 20/10/06, David Barron <[EMAIL PROTECTED]> wrote:
First, I really appreciated the build routine that is shown on the Introduction page. However since the routine is only displayed on the Introduction page it meant a lot of going back and forth in the browser. It would be nice if it was included on each of the pages where it should be used, like Xorg Protocol Headers, Xorg Utilities, Xorg Libraries, etc.
I half and half agree with this, since I've found myself doing exactly the same thing, although if you use elinks it's easy enough just to have 2 pages open, it may be considered excessive to have it on all pages since it's a relatively long command string that barely gets changed at all. Having done Xorg so many times I pretty much know the entire command off by heart, but like I said it barely gets changed at all, and scrolling back to the command in history and changing the wget file it uses is a good solution to this. I like the idea of the patches, but it feels more like something you'd put in a script, and as the amount of patches grows, so will the command, a more suitable command would probably be something like this; if [ -f ../../patches/$packagedir*.patch ] ; then for patch in ../../patches/$packagedir*.patch; do patch -Np1 -i ../../patches/$patch done fi P.S this works in zsh but not bash, bash spits out "bash: [: too many arguments", but zsh does the following; excaliber% if [ -f ../patches/procinfo*.patch ]; then for patch in ../patches/procinfo*.patch; do echo $patch done fi ../patches/procinfo-18-install-1.patch ../patches/procinfo-18-maxdevs-1.patch ../patches/procinfo-18-perl-1.patch ../patches/procinfo-18-uptime-1.patch ../patches/procinfo-18-use_sysconf-1.patch so if this were to be used someone will probably want to modify it to work around that, but you get the general idea. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
