Le 11/04/2012 20:56, Armin K. a écrit : > Hello there. I've been looking at Xorg build instructions lately. > > Introduction page includes little script that automates building of > every package in the section. > > Every package section have only configure (a bit different at some > stages), make and make install > > I'd suggest to merge that script into every xorg section, but with > introducing a risk that all packages must be configured and built as > root, unless someone can think of some other way. > > One reason for that are automated builders which parse xml for commands, > and another reason are users itself which build everything by hand, and > don't read instructions well. Believe me I've noticed someone just using > same script for every part of xorg, only changing wget file name, but > without modifying configure line in that script, hence screwing build up > somehow. > > What do you think? As you may know, I have been working on an automated builder which parses xml. If you want to try it, it is at: svn://svn.linuxfromscratch.org/ALFS/jhalfs/branches/ablfs It works pretty well now, specially concerning dependencies, but it is impossible to have it completely automated, and the scripts need reviewing.
It works pretty well with Xorg packages, except the link instructions in Xorg-fonts. It is very hard for an automatic parser to understand that they should be run only once. Maybe, they could be moved to a "configuration" section. The reason why it works is that the introduction script has been hardcoded (not my work actually, M Esparcia did it 5 years ago) into the xsl stylesheet. This means that if that script is changed for some reason, it will not make its way into the builder until somebody changes the stylesheet. Of course, the problem is different for copy and paste builders. I do not have much experience in that matter. Now, if you put the loop on each page, the stylesheet will need some rewriting, but it should be easy. For not configuring and building as root, you may use a variable, say SUDO, and put something like `$SUDO make install' for commands needing to be run as root. If the user decides to build as root, (s)he does not define SUDO, If (s)he wants to build as user then, (s)he can have `SUDO=sudo <options>'. Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
