1 |
On Mon, Jul 30, 2012 at 11:16 AM, Mike Gilbert <floppym@g.o> wrote: |
2 |
> On Mon, Jul 30, 2012 at 12:05 PM, Matthew Summers |
3 |
> <quantumsummers@g.o> wrote: |
4 |
>> Could we not just set a dep as =dev-lang/python:2 so that any version |
5 |
>> of python-2.* would satisfy the dep? Or, would this cause issues in |
6 |
>> avoiding old versions of python (python-2.5)? It might be enough to |
7 |
>> change the portage ebuild to work as it does now for the USE python2 |
8 |
>> and python3, but in the case where those flags are not set, then just |
9 |
>> pull in python:2 which would yield the latest stable version of |
10 |
>> python-2.* |
11 |
> |
12 |
> Using an || dep with to separate =dev-lang/python-2* and |
13 |
> =dev-lang/python-3* (or something roughly equivalent) is enough to |
14 |
> trigger the desired behavior from portage. See my previous message in |
15 |
> this thread. |
16 |
> |
17 |
>> For python-updater, I might be inclined to add similar USE to portage |
18 |
>> to manage the deps. |
19 |
> |
20 |
> No need for the use-flags. Again, I think the || dep is sufficient. |
21 |
> |
22 |
|
23 |
Yes, that makes sense, its a matter of order then. |
24 |
|
25 |
-- |
26 |
Matthew W. Summers |
27 |
Gentoo Foundation Inc. |