1 |
* Mike Gilbert: |
2 |
|
3 |
> Speaking on behalf of the python team, we are not particularly keen on |
4 |
> maintaining libraries that are only used by a single package. We have |
5 |
> too many packages to care for already. |
6 |
|
7 |
I agree. I know about the various risks of dynamically installing |
8 |
dependencies, but "pip install X" in virtual environments is very useful |
9 |
nonetheless. Gentoo does not offer an equivalent (I'm not judging, just |
10 |
saying), and it seems to me that is causing the Python team a large |
11 |
amount of work, eating up resources that could be spent elsewhere. |
12 |
|
13 |
> Not everything needs to be handled in an ebuild; often it just |
14 |
> increases the amount of busy work you end up doing. |
15 |
|
16 |
Ebuilds are great when an application needs config files, init scripts, |
17 |
users/groups, and when app A connects to app B (for example, if there is |
18 |
a milter there will also be an MTA calling it). |
19 |
|
20 |
Two of the milters I am using happen to be written in Python. One |
21 |
requires pymilter, so I created a PR introducing a pymilter ebuild. I'd |
22 |
rather avoid that ebuild, because pymilter is an interface to libmilter |
23 |
and of little use of its own, but other apps depend on it. |
24 |
|
25 |
-Ralph |