On Tue, Jun 12, 2018 at 01:49:25PM +0100, Chavdar Ivanov wrote:
> I think something along these lines should be preferable - in the presence
> of a native package installer capable of working for an individual non-root
> user, to try to minimise the corresponding content in pkgsrc.
Crippling pkgsrc is a no-go. Especially with "native" package installers
that don't have any way of ensuring content integrity.
I may have been misunderstood. I am not advocating for pip, I am just saying that IF a python extension does not depend on anything beyond the standard python library && no other packages depend on this extension && this extension is not of universal wide interest && this extension happens to be easy to install with pip THEN maybe it would be easier for pkgsrc development if it is left for pip installation in virtualenv. Solely with the rationale of keeping pkgsrc sane and not populating it with many thousands of python extensions with limited universal interest. But of course this is pkgsrc developers' choice, if they can afford to maintain them, following the latest versions as and when released, this is fine. Obviously messing with pip by installing extensions in the common pkgsrc system areas would be undesirable, that's why I underlined the use of virtualenv.
> The other day I tried to build py-matplotlib with the graphical
> interfaces with pkgsrc on an OpenSUSE Tumbleweed system, everything in
> the build went right, but at the end no graphic window appears when the
> test program is invoked... The native 'pip3 install matplotlib' worked of course.
Let me guess: you don't have all of the necessary development headers
installed, so pkgsrc tries to install its own set. At the same time, the
f**ked up shared library lookup in some Python extensions decided that
it should mix in part of the "base" system and havoc resulted. That's
not really an argument in favor of pip, just an argument in favor of
kicking upstreams.
I am sure I have messed something up and there may have been something missing in my base OS installation, I might boot this system later to try to find out what. It was OpenSUSE Tumbleweed after all, it gets updated several times a month and something may have gone astray. On this system there are python2.7 and 3.6.5 + many extensions both with zypper and pip, also separate python2.7 and 3.6.5 from pkgsrc (again with many extensions), and on top of that beta of python3.7 and early version of python3.8 built from scratch. It is not hard to get messed up... I am now going to test it under -current from yesterday with perhaps saner environment.
Joerg
Chavdar