1 |
Am Mittwoch 29 Februar 2012, 21:24:49 schrieb Krzysztof Pawlik: |
2 |
> > Second, there doesn't seem to be any support for packages that do not |
3 |
> > install in python's site-packages and do not allow multiple python ABIs. |
4 |
> > If I have, for example, a package that installs python modules |
5 |
> > in /usr/lib/appname or /usr/share/appname, how can I specify that |
6 |
> > PYTHON_TARGETS="python2.6" or "python2.7" or "python3.2" is allowed, but |
7 |
> > something like PYTHON_TARGETS="python2.7 python3.2" is not? |
8 |
> |
9 |
> You're correct, note that I've stressed that this eclass is mainly for |
10 |
> distutils-based packages. I'm not using Gnome, so can you provide some |
11 |
> package examples that I can look at? |
12 |
> |
13 |
> <personal opinion> |
14 |
> If package decides to use given language then please, please play by the |
15 |
> rules set by the rest of world (Ruby -> gems, Python -> distutils, Perl -> |
16 |
> CPAN, PHP -> PEAR). |
17 |
> |
18 |
> I don't like installing Python code outside of site-packages, the only |
19 |
> exception to that rule is portage (at least for now). |
20 |
> </personal opinion> |
21 |
|
22 |
We will hit the same problem with KDE (actually we already hit it): it has |
23 |
various types of scripting support, and each installs a KDE library linked to |
24 |
whatever language interpreter. |
25 |
|
26 |
(Now, that library- is it a Python/Ruby library or a KDE library? Because it |
27 |
is at the proper place for KDE stuff :) |
28 |
|
29 |
It's not just about calling an external language but also about embedding the |
30 |
interpreter for in-app scripting... and KDE rather heavily relies on python. |
31 |
|
32 |
-- |
33 |
|
34 |
Andreas K. Huettel |
35 |
Gentoo Linux developer |
36 |
dilfridge@g.o |
37 |
http://www.akhuettel.de/ |