Portage Questions

[Eckos]

Is there a way to keep --nodeps from removing a gcc version from there when I have multiple versions? Even if I accently forget to set the option?

I have virtualbox and it won't work with gcc-4.3.1 and was wondering how can I make portage when I do a -e world it would compile it with 4.2.4 and not 4.3.1 only on that package and switch to 4.3.1 on everything else?

[wim-x]

I don't know if portage can do that, I don't think so.

I would first compile virtualbox with gcc-4.2.4 using gcc-config, and then switch back to gcc-4.3.1 and emerge world.

[Eckos]

I don't know if portage can do that, I don't think so.

I would first compile virtualbox with gcc-4.2.4 using gcc-config, and then switch back to gcc-4.3.1 and emerge world.

But then it would fail if I did a emerge -e world

[wim-x]

But then it would fail if I did a emerge -e world

I'm assuming it fails on the virtualbox which then gets compiled with the gcc-4.3.1. What if you put virtualbox in package.mask after you install it with gcc-4.2.4 and then emerge -e world?

[Carlo]

Is there a way to keep --nodeps from removing a gcc version from there when I have multiple versions? Even if I accently forget to set the option?

Don't use --nodeps. There is no sane reason to do so. It's unsafe. Just don't.

I have virtualbox and it won't work with gcc-4.3.1 and was wondering how can I make portage when I do a -e world it would compile it with 4.2.4 and not 4.3.1 only on that package and switch to 4.3.1 on everything else?

I don't really get you here... Virtualbox doesn't compile with GCC 4.x at the moment afaik. I'm a bit lost what this may have do with using --nodeps.