On Tue, Feb 10, 2015 at 11:10:22PM -0800, Paul Rogers wrote: > Got 188 packages installed. Next I guess it's the GTK path, getting to > Firefox. I'm using 15.0.1 now. Looks like 24esr or 31.4esr should be > my goal. That's a bigger jump than I normally like to make. I looked > at the config.in for the prereqs. Mostly the same, though in my > experience there's usually a thing or two not in that list. The BLFS > I'm using for my LFS-7.2 recommends Pango-1.32, greater than the 1.14 or > 1.22 they require, so thats good. It also had me install sqlite-3.7.14. > 24esr wants sqlite-3.7.17, and 31esr wants sqlite-3.8.4.2. I don't > suppose 3.7.17 should be a problem. My question is, with this 7.2 and > contemporaneous BLFS, will sqlite-3.8.4.2 be a "drop in"? And will I > have to go back and recompile everything already built for 3.7.14? TIA.
188 packages - you've probably completed Xorg. Latest fixes are for the server (1.17.1, 1.16.4), thought to apply to all versions since 1996 ;-) But you are somebody who cares about security, so I guess you are already on 1.16 (from memory, a small vulnerability announced in the last year, and a huge swathe announced the year before). Is firefox 24esr still supported ? Actually, I've never seen the point of the esr versions - in BLFS, particularly now that we have dropped xulrunner, very little needs to be rebuilt for a newer version of firefox. I suppose things are different for people using binary software. Certainly, when I used to use early gnome-2 versions of epiphany which used gecko as the rendering engine I had to rebuild them after each xulrunner update, and perhaps an esr version might have avoided that - of course, epiphany went to webkit years ago, and I stopped building it a long time ago after the gnome-3 changes made each new version less useful to me. Some people update everything in their current system, for a true rolling release. Me, I only fix vulnerabilities or bugs which I know and care about, so many things on my systems are in the as-initially-built stage. But there are a few BLFS things I always update, of which the main one is firefox - and for that I often update sqlite to current (that depends on the wording on the sqlite home page for the current version), plus I update nss, nspr, certificates - always to the current versions. Compare that to openssl where I keep within the same series when updating old systems (so, I only recently got rid of my 0.9.8 script when I labelled the last system using that as unmaintainable). Which means that _I_ have no qualms about dropping in the latest sqlite3. And although I have stopped maintaining my 7.2 system (the glibc vulnerability - not worth my time to fix it), I don't think its version of gcc had any particular issues with the firefox code base (unlike LFS-7.0 and 7.1 where some experimentation was needed, at least on x86_64). Maintain and enjoy. Oh, and if your system predates libjpeg-turbo, have fun! (for the 8.x version of the lib, the turbo solib is lower-numbered than the version from jpegsrc, ldconfig will remake the symlink to point to the higher version which causes issues with some forums in firefox - thumbnails do not render - until you correct the symlinks. If your system does predate jpeg-turbo, I would be inclined to remove jpeg and rebuild as necessary, fixing up the symlink after every install while I am still building the system would get me down. But I still think that starting from a version of BLFS which is more than 2 years old is a waste of your time for desktop systems. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
