> People on -support might remember that I used to update my recent > desktop systems for important vulnerability fixes (or for new > versions of my preferred browser - firefox), but that after > firefox-58 I was no-lomger able to update my oldest systems, and > gave up.
Firefox has been a PITA ever since the rapid cycles. > > In theory, BLFS is a rolling release, and therefore everybody > updates everything. I suggest that in practice nobody updates > everything. Au contraire. I do. I'd rather take the time and have everything consistent than end up even once having an obscure failure over some inconsistency. Documentation is virtually never entirely trustworthy, Packages that haven't changed already have functioning built scripts, so that's just spending cycles. Packages that have, have nearly ready build scripts. That I have to go through the book to check it all out and make updates is just good business. > > For various reasons, with the release of qt-5.12.0 (not yet in the > book, because although the full build including qtwebengine is fine, > building qtwebengine separately does not work : to my surprise, Wot?! Now we have to support GTK & QT BOTH?!?!?! > > This building everything rom source is a fun game, isn't it ? > > ĸen Not exactly, but it's the cost of having a chance at reasonable security, actually owning one's own computer. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
