1 |
On Sun, 06 Jun 2010 04:19:28 +0200 |
2 |
Sebastian Pipping <sping@g.o> wrote: |
3 |
|
4 |
> Thomas, |
5 |
> |
6 |
> |
7 |
> On 06/06/10 04:01, Thomas Sachau wrote: |
8 |
> > [..] so even if it is not pulled in during installation, it will be |
9 |
> > pulled in during world update. |
10 |
> |
11 |
> sounds right. Preventing this requires either masking or a |
12 |
> dont-pull-uninstalled-slots switch for portage (which I am not |
13 |
> suggesting), right? |
14 |
|
15 |
In fact, these two seem to be the most reasonable solutions |
16 |
for the problem. While this switch idea is more universal (and I guess |
17 |
-- not that hard to implement), masking should be simpler. |
18 |
|
19 |
> > Since python-3* is currently useless and not required for any |
20 |
> > package, the dependency should by default only pull in python-2* |
21 |
> > like this: |
22 |
> > |
23 |
> > =dev-lang/python-2* |
24 |
> > |
25 |
> > With that, the default way would not pull in a package, which is |
26 |
> > not needed or used. And if there will be any package, which really |
27 |
> > requires python-3*, it simply requests it in (R)DEPEND of the |
28 |
> > ebuild, which then would overwrite the default value of the eclass |
29 |
> > and pull in python-3*. |
30 |
> |
31 |
> That's an interesting idea. |
32 |
|
33 |
It sounds quite pointless to me. Forcing the packages to assume they |
34 |
don't support the newer version just because nothing requires it yet? |
35 |
|
36 |
> > Are there any reasons to pull in a package, which is not requested |
37 |
> > by the user, not required by any package and by default not used by |
38 |
> > any package? |
39 |
> |
40 |
> That a question I haven't seen answered before, either. Arfrever? |
41 |
|
42 |
It _is_ requested by user. User requested upgrade of all dependant |
43 |
packages, and here it goes. |
44 |
|
45 |
-- |
46 |
Best regards, |
47 |
Michał Górny |
48 |
|
49 |
<http://mgorny.alt.pl> |
50 |
<xmpp:mgorny@××××××.ru> |