On Κυρ, Φεβ 03, at 09:21 Alexander E. Patrakov wrote: > Hello, > > BLFS SVN still targets LFS-6.3 and is in a deep freeze due to this, and I > object > to this fact due to the following: > > People don't report incompatibilities, even as bad as "a package fails to > build > from source", as this is the case for GPM > (http://linuxfromscratch.org/pipermail/blfs-support/2007-October/063848.html > -
I was submitted a patch for this same reason(1), due that OPEN_MAX is no longer defined in the linux headers(2). Unfortunately it can't be applied in the current Book, because as you say the target is the stable LFS book, which the released kernel is 2.6.22*. This also affects at least xine-lib(in the bug you are already posted[3]), dvd-rw-tools and iputils (4) (not in the book). 1.http://linuxfromscratch.org/pipermail/patches/2007-December/003402.html 2.http://readlist.com/lists/vger.kernel.org/linux-kernel/73/365977.html 3.http://www.nabble.com/--xine-Bugs-1820958---Linux-2.6.23-header-change-breaks-build-for-xine-lib-td13683064.html 4.http://www.redhat.com/archives/fedora-extras-commits/2007-August/msg01642.html > Then, the freeze hurts multimedia applications. Xine-lib (in version 1.1.8) > got > a fix for "cracky" sound when playing low-bitrate internet radios > (http://bugs.debian.org/396881). FFMpeg in November got support for J-frames > in > WMV videos > (http://lists.mplayerhq.hu/pipermail/ffmpeg-cvslog/2007-November/010311.html), > > and today it started decoding interlaced H.264 videos (available from DVB-T > broadcasts) without visual artifacts. However, the version in the book is old > and doesn't support these important features. Besides, it has security bugs > (it > crashes on corrupted H.264 streams that one can obtain from DVB-T in > Yekaterinburg in areas with not-so-strong signal - now fixed). How can one > start > testing the new version when the book is in such deep freeze without even an > approximate timeline? There is no hope to fix this in the current Book. If we replace ffmpeg version with a current snapshot, the update will probably break other packages. At least it needs a reasonable time for testing. > > I.e., in less than a month, the only non-obsolete LFS book will be the > development version. So why target a soon-to-be-obsolete version of LFS now? > Maybe it is a better idea to state that the BLFS 6.3 release is not going to > happen at all, and retarget to LFS SVN? If there is no plans for a release, either we have to create a branch to target the LFS dev book or we have to do what you say. -- http://wiki.linuxfromscratch.org/blfs/wiki/Hacking -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
