1 |
On 12/30/2009 05:18 AM, Petteri Räty wrote: |
2 |
> You need to understand what the world set means. The world set is the |
3 |
> packages in /var/lib/portage/world and the sets from |
4 |
> /var/lib/portage/world_sets . From this follows that we can't change the |
5 |
> content of the world set as it's a user specific configuration issue. |
6 |
|
7 |
Just to clarify a little (the above is completely accurate, but it might |
8 |
not be obvious how portage works just from reading this): |
9 |
|
10 |
The world set is a list of every package that you've executed an emerge |
11 |
<package> command on, without a -1 on the command line. So, if you type |
12 |
emerge xterm, then xterm is in your world set. A package is removed |
13 |
from world if you uninstall it, or if you edit that file manually. |
14 |
|
15 |
Packages that are installed because they are needed by packages that you |
16 |
install are not added to world, unless you later manually emerge them |
17 |
without a -1 on the command line. |
18 |
|
19 |
The idea is that anything you explicitly ask for is something that |
20 |
portage will try to keep around for you, and anything you don't |
21 |
explicitly ask for is something that portage will try to get rid of if |
22 |
it isn't needed later. |
23 |
|
24 |
So, those ruby packages ended up in world because you emerged them. Any |
25 |
new version that goes stable/testing on those packages will consequently |
26 |
get pulled in by an emerge -u world. |
27 |
|
28 |
The real issue (as was pointed out) is that packages shouldn't even be |
29 |
marked for testing (let alone stable) if they don't actually build, or |
30 |
if they have serious problems. They should be masked, so that only |
31 |
those interested in developing/debugging the package get hit with it. |
32 |
|
33 |
I don't want to comment on the packages you listed in particular, but |
34 |
sometimes you can run into build issues due to a need to run |
35 |
revdep-rebuild, or lafilefixer, or to rebuild some library. I had an |
36 |
x86 chroot that absolutely refused to build imagemagick until I just |
37 |
reinstalled the whole thing from stage3 - probably some obscure |
38 |
library/compiler problem. So a build error might not reflect a problem |
39 |
with the package you're trying to build. Obviously we still try to |
40 |
avoid these kinds of issues and warn users when they are likely to happen. |
41 |
|
42 |
I'd continue to follow the bug, and if it seems like something like this |
43 |
isn't being resolved expediently feel free to contact the QA team: |
44 |
http://www.gentoo.org/proj/en/qa/ |
45 |
|
46 |
The QA team ensures that Gentoo quality policies are being followed and |
47 |
can poke maintainers or step in as appropriate. |
48 |
|
49 |
Note that I haven't reviewed the packages/bugs that are being discussed |
50 |
here, so none of this is targeted at anybody in particular. I'm just |
51 |
pointing out how things like this are supposed to work in general. |
52 |
|
53 |
Rich |