| 1 |
On Thursday 09 April 2009 07:48:45 Nikos Chantziaras wrote: |
| 2 |
> Volker Armin Hemmann wrote: |
| 3 |
> > On Donnerstag 09 April 2009, Valmor de Almeida wrote: |
| 4 |
> >> Hello, |
| 5 |
> >> |
| 6 |
> >> There are a couple of packages (ebuilds) in the portage tree that I |
| 7 |
> >> would like to eliminate completely from my system and not get them back |
| 8 |
> >> after an emerge --sync. Is this possible? |
| 9 |
> >> |
| 10 |
> >> Thanks, |
| 11 |
> >> |
| 12 |
> >> -- |
| 13 |
> >> Valmor |
| 14 |
> > |
| 15 |
> > is there a good reason to remove them, instead of masking? |
| 16 |
> |
| 17 |
> If you like spending half a day masking hundreds and hundreds of |
| 18 |
> packages using an inflated package.mask, then no, there's no good reason :) |
| 19 |
|
| 20 |
The OP said "a couple of packages", so package.mask is the best bet. |
| 21 |
|
| 22 |
PORTAGE_RSYNC_EXTRA_OPTS is probably not the best way - if one of those |
| 23 |
packages is in a DEPEND that is needed somewhere, portage will throw a hissy |
| 24 |
fit about missing stuff. If masked, at least you get a parseable error message |
| 25 |
|
| 26 |
-- |
| 27 |
alan dot mckinnon at gmail dot com |
Archives