On 15/10/2017 20:37, Bruce Dubbs wrote:
LFS now has four new packages: libffi, python3, ninja, and meson.
I have just removed dependency references in BLFS to these packages in
accordance with our overall policy.
The biggest change is for python3. It is still in blfs because it
optionally needs to be rebuilt with an optional dependency for one
package, asymptote, or possibly optional modules for packages not in
BLFS.
(Yes I know I used 'optional' three time in one sentence.)
In many places I have still left python2 as an optional dependency,
but that may not be used if python3 is present.
In any case, this large change may have issues. Please report any you
find here.
Maybe marginal to this thread, but it seems to me that Python3
documentation installation should stay in BLFS, rather than being moved
to LFS. The reason is that once users have built LFS, several versions
of Python might be released before they build LFS again. Since they are
likely to update using BLFS, documentation should be there. Actually,
Python documentation is not needed to get LFS running. The Python page
in LFS could just point to BLFS's one for documentation installation (as
we do for supplementary languages in GCC, for example).
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
