1 |
On Thu, 29 Dec 2011 08:50:11 -0500 |
2 |
Mike Gilbert <floppym@g.o> wrote: |
3 |
|
4 |
> On 12/29/2011 08:41 AM, Michał Górny wrote: |
5 |
> > On Thu, 29 Dec 2011 08:08:26 -0500 |
6 |
> > Mike Gilbert <floppym@g.o> wrote: |
7 |
> > |
8 |
> >> This patch allows python_mod_optimize to be used in cases where a |
9 |
> >> different set of python modules is installed depending on the |
10 |
> >> python abi. |
11 |
> >> |
12 |
> >> For example, dev-python/feedparse-5.1 (not yet in the tree) |
13 |
> >> installs the _feedparser_sgmllib.py module only in python-3*. |
14 |
> > |
15 |
> > Could you paste some example on how it is supposed to be used? |
16 |
> > |
17 |
> |
18 |
> Sure. Borrowed from feedparser-5.1.ebuild in Progress: |
19 |
> |
20 |
> pkg_postinst() { |
21 |
> python_mod_optimize -A "2.*" feedparser.py |
22 |
> python_mod_optimize -A "3.*" feedparser.py _feedparser_sgmllib.py |
23 |
> } |
24 |
> |
25 |
> pkg_postrm() { |
26 |
> python_mod_cleanup -A "2.*" feedparser.py |
27 |
> python_mod_cleanup -A "3.*" feedparser.py _feedparser_sgmllib.py |
28 |
> } |
29 |
|
30 |
Ok, now that I see it, I think you're inventing a really big hammer to |
31 |
get rid of a single mosquito. |
32 |
|
33 |
On the other hand, I don't think I can think of a good per-ebuild way |
34 |
to handle this. I'd rather start by pinging upstream not to pollute |
35 |
global namespace and install a package instead; even if it supposed to |
36 |
contain __init__.py only. |
37 |
|
38 |
-- |
39 |
Best regards, |
40 |
Michał Górny |