On 07/29/2012 05:48 PM, Bruce Dubbs wrote:
> Armin K. wrote:
>> On 07/29/2012 10:09 PM, [email protected] wrote:
>>> Author: dj
>>> Date: 2012-07-29 14:09:42 -0600 (Sun, 29 Jul 2012)
>>> New Revision: 10477
>>>
>>> Modified:
>>> trunk/BOOK/general.ent
>>> trunk/BOOK/introduction/welcome/changelog.xml
>>> trunk/BOOK/x/installing/installing.xml
>>> trunk/BOOK/x/installing/x7app.xml
>>> trunk/BOOK/x/installing/x7font.xml
>>> trunk/BOOK/x/installing/x7lib.xml
>>> trunk/BOOK/x/installing/x7proto.xml
>>> trunk/BOOK/x/installing/xorg-config.xml
>>> trunk/BOOK/x/installing/xorg7.xml
>>> Log:
>>> Removed external Xorg wget and md5sums files, and included for-in-do loops.
>>>
>> Um, not bad ... But I think we still should split the packages into
>> seperate ones (not including Xorg Applications) and add loop as an
>> option for unpatient ones.
Eventually that will happen, piece by piece. This only gets us passed
the added version number and gets all of the current instructions into
the book. I'm not sure that I understand why you want to make a special
case for xorg applications though.
>>
>> Also, I dislike the use of sudo by default there. It isn't even listed
>> in dependencies,
Sure it is...it is listed as recommended in both the introduction to
Xorg (as was wget) and for now in xorg-proto (the first group of
packages that use it), but I think we'll use Bruce's suggestion below to
make it completely optional.
>> and not everyone installs sudo. I have it installed,
>> but I don't like it and I rarely use it. I think we could use some kind
>> of variables to check wether:
>>
>> User would like to compile and install everything as root (with a BIG
>> warning),
>> wether to use sudo (with explanation that user should make his user not
>> to ask for password to speed up things)
>> or even to use su -c "make install" (Yes, it asks for password every time).
> Personally I do like sudo but I also understand Armin's point. I also
> prefer using pushd $packagedir ... popd to the cd constructs.
>
> For the install, we might want to consider something like:
>
> <as root> make install
>
> With a note/entity like:
>
> <!ENTITY as_root "<note><para>When installing multiple packages in
> a script, the installation needs to be done as root. There are three
> general options that can be used to do this:<para>
>
> <orderedlist>
> <listitem>Run the entire script as the root user. (not recommended)
> </listitem>
>
> <listitem>Use the <application>sudo</application> program (<ulink
> linkend='sudo') with or without methods for avoiding requests for the
> root password.</listitem>
>
> <listitem>Use <command>su -c make install</command> which will ask
> for the root passwords for every iteration of the loop.</listitem>
> </orderedlist></para>">
This could be reused elsewhere should the need arise again (though
orderedlist is giving me a fit in an entity).
>
> Just prior to the build commands. That is:
>
> &as_root;
>
> <screen><userinput>for ...
> packagedir=${package%.tar.bz2}
> tar -xf $package
> pushd $packagedir
> ./configure $XORG_CONFIG
> make
> <as root> make install
> popd
> rm -r $packagedir
> done</userinput></screen>
>
> -- Bruce
I think that should meet everyone's expectations.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
