I will be committing this shortly. This post is an explanation for
some of my decisions about the markup.
I am aware that some people update _everything_ in their current
system, for a rolling release. I'm not one of those people. I'm
also aware that some people never update package versions in their
build - I regard that as silly, and perhaps dangerous. Me, I build
a (desktop) system, use it as my main system for a while, and then
eventually build a newer system. But I try to keep my older systems,
particularly released LFS/BLFS versions, usable for some time - at a
minimum, my kernels should be using recent versions from a
still-supported version (or current -rc, with possible breakage!),
and firefox or xulrunner should be current.
So, I have minimally-usable versions of LFS 7.{0,1,2,3,4} although
some things (particularly gnome and any kde apps) are not
maintained.
With firefox-31.0, the Python part of the build system breaks if
HTTPSHandler is not found. That happens if you build Python-2
before openssl, which is what I have been doing for a few years
(never build a package until it is likely to be useful!). Normally,
we would just xref other packages. In this case, any recent version
of openssl fits the bill, so I have chosen my wording with care and
I will be very annoyed if anyone gratuitously changes it to imply
that only the current version of openssl is usable.
In the past, I have been wary about upgrading Python (it is not
obvious to me if anything after Python that creates extra modules
(e.g. xcb-proto, libxml2, py2cairo) needs to be reinstalled when
Python is upgraded). But with the 2.7 series (and 2.7 has been
needed for some time when building firefox), the installed
directiory is just python2.7 so a newer version will happily
overwrite the older version while installing its fixes. Therefore,
I have xref'd the current version of Python2 in my additions.
ĸ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/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
