On 06/11/2009 10:39 AM, Alan McKinnon wrote:
On Thursday 11 June 2009 05:18:18 Nikos Chantziaras wrote:
On 06/11/2009 06:11 AM, Nikos Chantziaras wrote:
I recommend putting "-python" in your make.conf followed by "emerge
-auDN world" and then a depclean along with revdev-rebuild.
You might have to enable python in a few packages after that though and
disable it in others. In my case:
echo "dev-libs/libxml2 python">> /etc/portage/package.use
Just follow the messages that tell you to enable the python USE flag in
specific packages. It's much cleaner to enable it only in packages that
actually need it rather than globally (which drags along PyQt and PyKDE.)
So is it more or less correct to say that USE=python gives you python plugins
for most packages? There could be other uses of course, but is that the most
common?
The flag itself is a global one and says "Adds support/bindings for the
Python language." That can mean a lot of things. Usually it's Python
bindings. And also usually, if you're not sure what it does, you don't
need it. If you enable something (like some cool looking plugin or
added functionality) that would require enabling the python flag,
portage will tell you so when you try to emerge. For example:
!!! Multiple package instances within a single package slot have been
!!! pulled into the dependency graph, resulting in a slot conflict:
[...]
New USE for 'dev-libs/libxml2:2' are incorrectly set. In order to
solve this, adjust USE to satisfy '>=dev-libs/libxml2-2.6.12[python]'.
Of course, the ebuild has to support this too, otherwise you will get a
compilation error when emerge goes ahead to tries to build the package.
