Fernando de Oliveira wrote:

What Alice prefers what we have for gcc: "For i686 systems, fix a
problem introduced by gcc-4.9.0."

This has about 100% of information, and as long is there, all newer
versions of gcc are also supposed to need the fix.

Incidentally, now, we have the following xml files with that gcc text:

multimedia/libdriv/gst-plugins-base.xml
multimedia/audioutils/lame.xml
postlfs/filesystems/mdadm.xml
general.ent
xsoft/office/libreoffice.xml

Alice told me that something should be done, or the book gets
unbalanced, inconsistent.

I agree with her: either we hide the information in the pages above,
necessary for the user to know if it is relevant, or fix the commit
14653, not to the previous state, but to what is now used for GCC:

-      If building with --enable-freetype2 configure switch, use the
following
-      <command>sed</command> to fix building against newer versions of
-      <application>FreeType</application>:
+      If building with --enable-freetype2 configure switch, use the
following
+      <command>sed</command> to fix building against
+      <application>FreeType-2.5.1</application> or newer versions:

Without it, the book is much clearly wrong!

I would like to thank Alice and Alex for discussions that allowed me to
think in a more logical way, because thinking with anger is difficult
and leads one to hell.

I would like to rewrite that Bruce has the reason: I am tired, but not
less than when he stated it. I will try to do some work today, but speed
and correctness will suffer very much.

Please go ahead and fix the book the way you have discussed. It seams reasonable to list the first known package version where a fix is needed. However, I submit that we can't always tell.

Also, If a new package version is added to the book, a fix may be incorporated and our fix is no longer applicable. We really don't want to add notes to the book about prior versions. In that case, it is really up to the user to upgrade the package.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to