#11549: Review dependencies on Python 2
-----------------------------+------------------------
Reporter: pierre.labastie | Owner: blfs-book
Type: enhancement | Status: new
Priority: normal | Milestone: x-future
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: Python 2 |
-----------------------------+------------------------
Comment (by pierre.labastie):
Replying to [comment:11 bdubbs]:
>
> Unless we know about a P2 dependency, then we can omit it by default if
it takes a command to include it. I'd say leave in the P3 bindings as we
have P3 already in LFS, but make P2 optional and don't take explicit
action to disable the P2 bindings.
There is an issue with this approach:
- suppose P2 is present. The package will then try to build say, bindings
for P2. If in the process, a python module is needed, this module must
have been built with P2. This means that all the python modules would have
to be built for P2 as well a for P3. I'd rather avoid that.
I think it's better to try to prevent P2 to come into the picture each
time it is possible: otherwise, we'll always have to build P2 bindings
(and so recommend P2), "just in case".
>Looking at ./configure --help for volume_key, it looks like picking up P2
is automatic if it is present, so we probably only need to move P2 to
optional.
But the problem is, in this case (for both P2 and P3 actually): if the
build system wants to build the python bindings, it'll need swig, and
since swig is not tested by configure, it will fail during the "make"
stage. OK, let's do it this way:
- P2 optional, swig recommended, others required as already noted. pass
--without-python (disable only P2) and comment about the --without-
python{,3} in command explanations.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/11549#comment:12>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
