1 |
14.08.2013 17:02, Michał Górny пишет: |
2 |
> Dnia 2013-08-14, o godz. 16:53:17 |
3 |
> Sergey Popov <pinkbyte@g.o> napisał(a): |
4 |
> |
5 |
>> 14.08.2013 16:05, Rich Freeman пишет: |
6 |
>>> On Wed, Aug 14, 2013 at 7:42 AM, Michael Palimaka <kensington@g.o> wrote: |
7 |
>>> Right now, however, |
8 |
>>> it might be useful if only to get a sense for how they're being used, |
9 |
>>> trade ideas, etc. |
10 |
>> |
11 |
>> Well, we can use sets as replacement for metapackages(for example, |
12 |
>> qt-meta, leechcraft-meta). |
13 |
>> |
14 |
>> Well, as for leechcraft-meta, we can not simply replace metapackage with |
15 |
>> set, cause we have unstable USE-flag there. |
16 |
> |
17 |
> No, we can't. Sets are portage-specific, the tree needs to follow PMS. |
18 |
> |
19 |
|
20 |
I am all for the standarts, but as we did not brought sets to PMS |
21 |
yet(when we updated it for EAPI changes), my question is: 'why?'. It is |
22 |
one of the long-standing feature of quite experimental 2.2_alpha branch, |
23 |
that should finally come to release(Thanks to portage team, by the way :-)). |
24 |
|
25 |
Why it was not added as a part of the PMS? Some implementation flaws? Or |
26 |
maybe, architecture problems? |
27 |
|
28 |
-- |
29 |
Best regards, Sergey Popov |
30 |
Gentoo developer |
31 |
Gentoo Desktop Effects project lead |
32 |
Gentoo Qt project lead |
33 |
Gentoo Proxy maintainers project lead |