1 |
On Mon, 15 Aug 2011 19:42:01 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
|
4 |
> On 08/15/2011 11:41 AM, Michał Górny wrote: |
5 |
> > Hello, |
6 |
> > |
7 |
> > Now that we don't have any old-style virtuals in gx86 anymore, |
8 |
> > I think the 'virtual' category is basically one another plain |
9 |
> > category nowadays. |
10 |
> |
11 |
> In sys-apps/portage, the "virtual" category is used as a hint to the |
12 |
> dependency resolver it needs to look ahead in order to make the best |
13 |
> possible choices. For example, in order to solve bug #141118 [1], it |
14 |
> recursively expands virtual/jre and virtual/jdk in order to |
15 |
> efficiently satisfy a jre dependency with whatever jdk happens to be |
16 |
> installed, instead of pulling in a redundant jre. |
17 |
|
18 |
Isn't that another, ugly, non-PMS hack which makes people think they |
19 |
are creating correct packages? |
20 |
|
21 |
> > Considering the number of different virtuals in this category, |
22 |
> > maybe it would be a good idea to split it a little? What I'm |
23 |
> > proposing is maybe creating some kind of '*-virtual' categories. |
24 |
> > |
25 |
> > For example, half of the current virtuals are prefixed with 'perl-'. |
26 |
> > Maybe they could be transformed into 'perl-virtual/*'? |
27 |
> |
28 |
> If you're going to do that, then I'd suggest giving them some sort of |
29 |
> tag that the package manager can rely upon in order to identify them |
30 |
> as virtuals. For example, we could have the ebuilds set |
31 |
> PROPERTIES=virtual [2], or we could simply specify (in PMS) that any |
32 |
> category whose name matches the '*-virtual' pattern will contain |
33 |
> virtuals. |
34 |
|
35 |
Doesn't DEFINED_PHASES==- serve that purpose nowadays? |
36 |
|
37 |
> [1] http://bugs.gentoo.org/show_bug.cgi?id=141118 |
38 |
> [2] |
39 |
> http://archives.gentoo.org/gentoo-dev/msg_9d449a18a96a25a547fcfd40544085cf.xml |
40 |
|
41 |
|
42 |
|
43 |
-- |
44 |
Best regards, |
45 |
Michał Górny |