On 10/20/06, David Barron <[EMAIL PROTECTED]> wrote:
Going through the Xorg 7.1 install, both manually and using jhalfs, I had a
couple of thoughts that might make things a little easier.
Thanks for your thoughts, David.
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. Doing that leads to my second
idea.
Having the routine on each page would make it easier to modify it to work
correctly depending on different needs.
For example, the Xorg Libraries wget list downloads 44 libraries and 3 patch
files. The script that jhalfs builds fails because it tries to applies the
patch every time it untars and builds a library. So I modified the routine to
look like this:
for package in $(cat ../lib-7.1.wget) ; do
packagedir=$(echo $package | sed 's/.tar.bz2//')
tar -xf $package
cd $packagedir
if [ "${packagedir}" == xtrans-1.0.0 ] ; then
patch -Np1 -i ../xtrans-1.0.0-setuid-1.patch
fi
if [ "${packagedir}" == libX11-1.0.1 ] ; then
patch -Np1 -i ../libX11-1.0.1-setuid-1.patch
fi
if [ "${packagedir}" == libXfont-1.1.0 ] ; then
patch -Np1 -i ../libXfont-1.1.0-cidfonts-1.patch
fi
./configure $XORG_CONFIG &&
make
make install &&
ldconfig
cd ..
rm -rf $packagedir
done
Ldconfig
Obviously, the idea is for the patch to only be applied to the right library.
Right. This makes a lot of sense and is a lot better than the crap
that I had to put in the book for those patches. However...
The BLFS book is really not about scripting. A very special exception
was made for Xorg-7 because it is so huge that this is the only way to
realistically manage it. This stinks for jhalfs and scripters in
general, but you have to remember what the intended audience is. I'm
OK with putting this in, but the other editors need to agree, and I'm
not sure about the chances of that happening.
That said, if you open a ticket in Trac, you'll be sure to get all the
active editors' attention and this won't be forgotten.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
