| 1 |
> Automatic upgrades like this isn't safe. |
| 2 |
Thanks! Won't do that again! |
| 3 |
|
| 4 |
> Complete recompilation of toolchain needed not every 6-9 months, but only |
| 5 |
> if one of toolchain packages was upgraded (and I think if just revision |
| 6 |
> (-r) number was changed then toolchain recompilation isn't necessary). |
| 7 |
> Anyway, there exists more correct and fast way to recompile everything: |
| 8 |
> # Recommended: cleanup your "packages" directory (usually |
| 9 |
> # /usr/portage/packages/) before continue to avoid installing wrong |
| 10 |
> # packages using -k by accident. |
| 11 |
By "cleanup", do you mean to "delete" what I don't need? |
| 12 |
|
| 13 |
> emerge linux-headers glibc binutils gcc-config gcc |
| 14 |
> # Here you should choose new gcc if it was installed into new SLOT! |
| 15 |
> gcc-config NAME_OR_NUMBER # see `gcc-config -l` |
| 16 |
> source /etc/profile |
| 17 |
> emerge -1 libtool |
| 18 |
> emerge -b glibc binutils gcc portage |
| 19 |
> emerge -bke system # avoid 3rd toolchain recompilation |
| 20 |
> emerge -ke world # avoid 2nd system recompilation |
| 21 |
> |
| 22 |
> Also I don't recommend to execute --depclean automatically, it sometimes |
| 23 |
> tries to uninstall too much including some important/critical packages. |
| 24 |
> |
| 25 |
> In addition to your commands I recommend to run glsa-check because there |
| 26 |
> can be some old non-ungraded packages in SLOTs which require manual action |
| 27 |
> for upgrade (like `emerge -uD "<package-version"`) or delete and which can |
| 28 |
> have security holes. |
| 29 |
The above is what I am looking for, thanks again! |
| 30 |
Cheers, Kwon |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-hardened@g.o mailing list |
Archives