Am 2019-04-10 14:34, schrieb Pierre Labastie via lfs-dev:
On 10/04/2019 12:30, thomas via lfs-dev wrote:
Am 2019-04-10 12:03, schrieb Pierre Labastie via lfs-dev:
On 10/04/2019 11:09, Julien Lepiller via lfs-dev wrote:
Hi!
I've helped a few lfs newcomers on the French IRC channel who all
made the same mistake: because there are two python archives, they
decompressed the wrong one and got stuck. It's not hard to imagine
them doing tar xf python<tab>. The tarball is actually named
Python-&python-version;.tar.xz with an upper-case letter. Since a
few users don't pay enough attention (and I can't blame them for
that) I'd like to suggest adding a note about the tarball name. What
do you think?
Thank you!
+1, Seems useful. Waiting for others to comment.
Yes sure, everything what helps to prevent users from making errors is
good.
OTOH using the correct tarball as it is named in the book is not that
error-prone as some other strange seds in some other instructions. If
starting from an empty sources-dir, there is only a python-docs
tarball beside the Python tarball; so no version mismatch should occur
and if you accidently unpack the docs instead of the source, no
configure script appears. At least here user should recognize that
something went wrong.
Anyway, at least a small note might be added to the phyton
chapter(s?).
Sed are error prone, but they can be copy-paste'd. There is nothing
like that for unpacking the right tarball. And since Python is the
only tarball with an uppercase letter, it may not be obvious to test
that Python-x.x.x exists if python-x.x.x does not. Do you want me to
try to write the note?
In the meanwhile we typed 10 times more letters than such a note would
have required ;-)
I'm not against adding such a note, but I'd like to say the described
error came from having not read/followed the book and not from a big
inaccuracy of the book...
--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page