Hi Randy,
On Wednesday 15 March 2006 17:51, Randy McMurchy wrote:
>...
> ./configure --prefix=$(kde-config --prefix)
>
> This way, you are essentially assured that the entire KDE
> installation will be in the correct prefix, even if someone later
> resumes installing KDE and forgets to set the $KDE_PREFIX.
Hmm, here you may assume that the install is done in the command line by using
copy&paste from the book. I don't believe that. I think most of the people
will have created their own scripts, makefiles or whatever to get the build a
bit more comfortable (since most of the people will have just finished their
LFS lesson). If that is true, I assume the scripts etc. will setup the
environment proper before doing the configure. If someone just copy&paste the
instructions without reading what he copies, I think it is a good educational
experience to run a build with an empty $XXX_PREFIX and discover what
happens. The otherone who read the commands before hitting the Enter key
should have just a nanosecond to think about the $XXX_PREFIX and whether it
is set or not.
> This to me is especially important for KDE as there is only 3 packages
> to be installed for a base KDE system. It might be weeks or months
> until another one of the optional KDE packages is installed.
Should be no problem if the above is true.
> Thoughts?
Anyway, it's surely ok to get the instructions look similar. So go ahead,
there is nothing wrong with it.
It was just my two cents worth.
Cheers,
Thomas
(Moody)
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
