| 1 |
2009/12/1 Mansour Moufid <mansourmoufid@×××××.com> |
| 2 |
|
| 3 |
> |
| 4 |
> You really shouldn't unmerge Portage, but if you want to, it should be |
| 5 |
> the last step -- coming *after* emerge -uUDN world && emerge |
| 6 |
> --depclean && revdep-rebuild. After which you can safely rm -drf |
| 7 |
> /usr/portage. |
| 8 |
> |
| 9 |
|
| 10 |
I get the way you would do the things, but that's quite the same thing that |
| 11 |
catalyst do behind the scene. |
| 12 |
But it uses a cache system that avoid re-emerging too often. |
| 13 |
That's chrooting a stage3, emerging fancy features, then removing others, |
| 14 |
all of this according to profiles. |
| 15 |
I thing that's not very maintainable and that's error prone (because you're |
| 16 |
not sure of what is unmerged, or what dependencies it could break). |
| 17 |
|
| 18 |
Anyway, thanks for your help that brings fresh meat to me. |
| 19 |
I'm interrested if there's a magic command to unmerge & clean every dev |
| 20 |
related things once system is built. |
| 21 |
|
| 22 |
ONE OFF-TOPIC MORE GENERAL QUESTION : |
| 23 |
Is there a gentoo hardened toolchain with SSP and PIE BEFORE gcc 4 ? |
| 24 |
|
| 25 |
-- |
| 26 |
Pierre. |
| 27 |
"Sometimes when I'm talking, my words can't keep up with my thoughts. I |
| 28 |
wonder why we think faster than we speak. Probably so we can think twice." - |
| 29 |
Bill Watterson |
Archives