How to 'emerge -e world' for all but one package

[chrisstankevitz]

Hello,

I want to rebuild every package on my system except one. the package I do not want to build is app-emulation/virtualbox-ose-2.0.4

Is this possible?

Thank you,

Chris

PS: The ebuild in question dies because my gcc-config points to GCC 4.3.2

PPS: My current approach is:
emerge -e world
[wait 4 hours for failure]
emerge --resume --skipfirst
[wait 4 hours for completion]

[Genone]

Assuming that package is listed in your worldfile and not a dependency of another package you could just remove it from the worldfile temporary. Or with the latest portage-2.2 rc use the following command to get the same effect without editing a file:

Code: Select all

emerge '@world-@foo{class=base.DummyPackageSet,packages=app-emulation/virtualbox-ose}'

(that syntax creates a temporary packageset @foo with the given package and removes its content from the @world set)

[gerard27]

When will we get docs for portage-2.2 and EAPI-2?
Gerard.

[gringo]

emerge '@world-@foo{class=base.DummyPackageSet,packages=app-emulation/virtualbox-ose}'

a bit ugly but thanks for that anyways - i think i never emerge world f.ex. and one app that i liked much was pye ( "pick your emerge") which allowed me to just pick those packages i wanted/ needed and would also be helpful for Gerard i think. Such feature would be much apreciated in future portage versions !
( can´t find a better link -> http://emresaglam.com/blog/171)

thanks !

[Genone]

emerge '@world-@foo{class=base.DummyPackageSet,packages=app-emulation/virtualbox-ose}'

a bit ugly but thanks for that anyway

Well, it's not exactly the primary use case for that syntax. The main purpose is to pass arguments to package sets (e.g. to rebuild all packages linked against a specific library, or all packages depending on a given package) without having to edit config files or setting env variables all the time. The ability to define new package sets on the fly was just added as a bonus

[gringo]

Well, it's not exactly the primary use case for that syntax. The main purpose is to pass arguments to package sets (e.g. to rebuild all packages linked against a specific library, or all packages depending on a given package) without having to edit config files or setting env variables all the time. The ability to define new package sets on the fly was just added as a bonus

yeah, very instructive indeed, like most of your posts in this forums

thanks !

[Elbar Thera]

Hi,

concerning your approach you can try something like this:

Code: Select all

emerge -e @world ; while (($? == 1)) ; do emerge --skipfirst ; done

Does the trick for me,
Elbar

PS: You must have a nice computer, because the last time i did a emerge @installed it took me nearly 3 days

[d2_racing]

When will we get docs for portage-2.2 and EAPI-2?
Gerard.

In fact, I will read that for sure

[gringo]

i suppose there´s more info somewhere but this and this (pdf) are worth a reading imo.

cheers

[gerard27]

Thanks gringo!
But I still would like to see something in the official Gentoo Docs.
Gerard.

[gringo]

Thanks gringo!
But I still would like to see something in the official Gentoo Docs.
Gerard.

yes, i agree, some kind of official documentation would be nice to have ( if not available already), although i don´t expect much difference with what is being explained in Ciaran´s blog or in the pdf hosted at Ferdy´s workspace. All package managers should implement this now iirc.

cheers guys

[d2_racing]

Thanks for the link