#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:7 renodr]:
 > I think that optional python bindings should be built irregardless of
 whether or not they are actually used by anything in the book. It
 simplifies maintenance in the future if they are actually required at some
 point, and doesn't hurt anything.
 >

 Well, in theory, I agree with this. In practice, it is not always simple
 (python bindings for gpgme require gnupg2 and swig to be present, python
 bindings for volume_key require swig, etc). I'll try my best to make
 everything coherent... But I think that hidden things is not what we want
 in blfs: the whole object of lfs/blfs is to control what is on the
 machine. We should try not to give up on this, otherwise, there will be no
 difference with any other distro...

 > Also - Upstream is good at hiding dependencies on python bindings -
 especially in GNOME. Udisks2 does use Python internally, as does gvfs.

 Actually, Udisks2 tests seem to require pygobject (the gi module). This is
 not noted in the book (will investigate).

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/11549#comment:9>
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

Reply via email to