Re: Minor Version increments
Well... On Fri, 7 Mar 2008 09:55:47 -0600 David Jensen [EMAIL PROTECTED] wrote: export FFVer=`grep MOZ_CO_TAG.*= client.mk \ | cut -d_ --output-delimiter=. -f4,5,6,7` this may be a bit radical. maybe: export FFVer=firefox-version the user could edit to suit. in commands place $FFVer where we now substitute firefox-version. I tried this, albeit with a different variable name, the book renders: snip export FireFoxVers=2.0.0.6 /snip ... snip make -f client.mk install install -v -m755 -d /usr/lib/firefox-$FireFoxVers/chrome/icons/default ln -v -s ../../../icons/default.xpm \ /usr/lib/firefox-$FireFoxVers/chrome/icons/default chown -v -R root:root \ /usr/lib/firefox-$FireFoxVers/extensions/[EMAIL PROTECTED]/* /snip fwiw David Jensen -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Minor Version increments
On Fri, 07 Mar 2008 10:07:46 -0600 Randy McMurchy [EMAIL PROTECTED] wrote: That way, the instructions would copy and paste for a newer version. A convenience for the user, and less updating pressure for Editors. I'm not a big fan of this as it sort of implies we support (have tested) newer versions than what the book has in it. Additionally, there are so many minor nuances (Moz packages might be an exception as they normally don't require command changes) that things could be a bit different (doc creation, test suites, installed files, etc.). Indeed, I backed off a bit. But for my own convenience I'd like to see all the 'hard-coded' versioning go. But, handiling 'patch' versions (for one) would be a pita. Maybe later. David Jensen -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Minor Version increments
Robert Daniels wrote: On Friday 07 March 2008 10:07:46 Randy McMurchy wrote: I'm not a big fan of this as it sort of implies we support (have tested) newer versions than what the book has in it. Additionally, there are so many minor nuances (Moz packages might be an exception as they normally don't require command changes) that things could be a bit different (doc creation, test suites, installed files, etc.). I am in agreement with this. I believe I said this elsewhere, but I can't find the message right now. What BLFS provides is instructions known to work with a specific version of a package. The user is welcome to try the same instructions on a later version of the package. It will likely work, but we have not tested it and can therefore make no guarantees. Well, the new instructions I am working on for autofs will pull an arbitrary number of patches from kernel.org and build with those: Recommended Patches: There are frequent patches issued for autofs. To get the current patches, start in the same directory as the main tar file and run: wget http://ftp.kernel.org/pub/linux/daemons/autofs/v5/patch_order-5.0.3 sed 's;autofs;http://ftp.kernel.org/pub/linux/daemons/autofs/v5/autofs;' patch_order-5.0.3 wget-list wget -i wget-list for f in `cat ../patch_order-5.0.3`; do patch -Np1 -i ../$f done That's the way they distribute patches instead of rolling the version. They've had 15 patches since 14-Jan-2008. Of course when they do roll the version, the book will need to change, but technically, I'm relying on the upstream devs to get the patches right. If they put in a new patch, technically I haven't tested it, but I'll rely on bug reports if there is a problem. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
