-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/11/2013 02:22 PM, Matt Turner wrote: > On Thu, Apr 11, 2013 at 10:09 AM, W. Trevor King <[email protected]> wrote: >> In order to avoid problems like this, it's probably a >> good idea to remove all the cached stuff with something like [1]: >> >> $ rm -rf --one-file-system /var/tmp/catalyst/{kerncache,packages,tmp} >> >> before building your stage1. > > Not sure this is the way to go. I'll have to think through the > implications. Consider your stage1 build dies with some stupid tree > breakage that you can fix in your portage snapshot and restart the > stage build. This is going to cause your stage to rebuild everything. > > Wouldn't disabling the use of binary packages during the seed stage > update fix this? > > I'm not sure I'd call rebuilding it every time a "fix" when you just rejected deleting the bad packages and rebuilding ONCE.
As I said, the only proper fix is to update the toolchain to EAPI5. We could live in the dark ages forever, but I really don't think it helps anyone. - -ZC -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRZwajAAoJEKXdFCfdEflKqOcQAKo3MnuT1dZrEudaH2gC1g+f ++iAxgaA3TkwKJ7srhcI1R6Xvoyb4Iv/BNCYcwYQn1Ta0yS682qwFouP17YBDdIN vqAQViCK39YPwg3pY77IgwMa2KQSrnLIPM6jV05174QR3Og8otzvW3ur9ou8GQgz KTcRNhl7cPqajV8voq7u4WD05brLpvH2l5rP3UZliavsas3fopioORSdlaRTqicD MpxK2iXKx+qScwgEcoWelRIMG25U1f0KGcLDDIslfJ+YTZ3/9pRYePXpr8kZlp1O oegdNTCqH5wD80QoMSocAVahvCOjW/yyBYJFIfzQpzubPsodtVGr0k7hVaPZNZF7 kznW+E0j1HuW/K3hlRfLlhiYbcalXRCsQmzT9Qbenkq1HuR6KsHK3KWe0iipJvgO lU/TPty6TeXPczK9K7wqo1e5nuE39Z7AUvVIjaIJr1Y9QSWyMVfEQq3pO5x9Ity2 tIBGzYh11r/n3W9Sj5wfqN8GDGugNJmhJS1ytMKuOSRmDEkvOzaaubZBVja92FCQ DtcY1xLn/edax3ReYpRjLQSxuneKA8lsDCt3WYOedzF5KW2WbgV5XRXh8lS4jG3L UaayekUNQJImgbJu4hqqsbhnBEEHKHjxSdSaqD1xydE5KPCVSq00dsW2TKyv0sUT Y5XgK1g1Umxp42brFXG7 =jZeA -----END PGP SIGNATURE-----
