1 |
On Mon, Jun 27, 2011 at 20:23, Benedikt Böhm <hollow@g.o> wrote: |
2 |
> the way python applications are built currently renders all binary |
3 |
> packages useless, since portage does not know which version of python |
4 |
> it was built against. the explicit selection with RUBY_TARGETS or |
5 |
> PHP_TARGETS solves this problem at the small cost of commiting new |
6 |
> values to these variables from time to time. |
7 |
|
8 |
I don't think updating all Python packages every two years is a small |
9 |
cost, particularly when a large percentage of those packages will just |
10 |
work on the new version. |
11 |
|
12 |
(Another problem with the current Ruby approach is that it's |
13 |
impossible to support unstable interpreters or versions from in stable |
14 |
package versions, such that Ruby packages now often have multiple |
15 |
ebuild revisions for stable and unstable interpreters.) |
16 |
|
17 |
Cheers, |
18 |
|
19 |
Dirkjan |