1 |
On 12/12/2012 06:53 AM, Francesco Turco wrote: |
2 |
> Hello. |
3 |
> |
4 |
> A couple of weeks ago I filed a bug because in the Installation Handbook |
5 |
> I found some references of the "world" set in emerge commands, as |
6 |
> opposed to "@world": https://bugs.gentoo.org/show_bug.cgi?id=445184 |
7 |
> |
8 |
> The bug was closed as invalid, and I was told that: |
9 |
> |
10 |
>> sets with the @ prefix are a portage-2.2 feature, which is still hardmasked and thus not documented. |
11 |
> |
12 |
> The fact is that I have portage-2.1.11.37, not 2.2, and man emerge says: |
13 |
> |
14 |
>> When used as arguments to emerge sets have to be prefixed with @ to be recognized. |
15 |
> |
16 |
> One possibility is that documentation stick with the stable portage |
17 |
> package, not the testing one (I have a ~amd64 system only). But I |
18 |
> checked portage 2.1.11.31 (the latest stable amd64 portage package |
19 |
> version) and the previous phrase is there, too. |
20 |
> |
21 |
> I know it's not a very important issue, but I'd still like to know if |
22 |
> I'm wrong or not, and why. |
23 |
> |
24 |
|
25 |
IMO you aren't wrong, but it isn't fixable right now. I see your point: |
26 |
using @system and @world is more consistent, and eliminates an |
27 |
additional thing that you have to remember. |
28 |
|
29 |
But right now, 'system' and 'world' are simply hard-coded magic strings. |
30 |
Until that changes, using @system and @world really conflates two |
31 |
different ideas: the magic system/world, and the portage-2.2 @sets. Some |
32 |
day they may be unified if we can, |
33 |
|
34 |
1. Move $PORTDIR/profiles/base/packages into @system |
35 |
|
36 |
2. Move /var/lib/portage/world into @world |
37 |
|
38 |
3. Not break everything in the process (this is the hard part) |
39 |
|
40 |
Afterwards I think they would be more receptive to updating the docs. |