Duncan wrote: > Thus, my suggestion. Why not create a second feature, toolchain-buildpkg, > I'm calling it here for purposes of developing the suggestion, that's on > by default, as contrasted to the normal buildpkg being off by default. > The Gentoo Handbook would then of course be modified to cover it and > mention why Gentoo recommends that it stay on. Portage would then always > buildpkg anything rescue-critical, including portage itself, gcc, > binutils, coreutils, python, etc. Don't forget glibc (which would of > course need put in place from a LiveCD, one's "emergency" copy of the root > partition, etc).
What is a probability that user running *stable* branch would bork his box by upgrades? Aren't those running ~ARCH expected to make backups? Is it such a problem to reboot their *testing* boxes from some CD and restore backups from such environment? (I know about special cases like machines w/o CD-ROM/netboot, but I think their owners are skilled enough to find other solution which better suits their needs.) Why bother with such a feature which won't be used by most of people, instead of doing something "more useful"? Just my 2 cents, though. -jkt -- cd /local/pub && more beer > /dev/mouth
signature.asc
Description: OpenPGP digital signature
