-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/28/2013 03:33 PM, Brian Dolbec wrote: > On Tue, 2013-05-28 at 14:50 -0400, Rick "Zero_Chaos" Farina wrote: >> On 05/28/2013 01:59 PM, Brian Dolbec wrote: > >>> Existing gcc binpkgs have been linked to libmpc.so.2 and portage does >>> not check that all lib links exist before qualifying the binpkg to be >>> installed. Therefore installing a gcc binpkg is a hit and miss >>> proposition. Making it's use un-reliable. Therefore until the >>> toolchain is migrated to eapi 5 with proper subslot use. Using binpkgs >>> is unreliable for update_seed. >> >> In fact, the command is "--rebuild-if-new-ver" not >> "--reinstall-if-new-ver". As such, the original reporter of this bug >> and I both seem to think that even with --usepkg, gcc should be rebuilt: >> >> https://bugs.gentoo.org/show_bug.cgi?id=461422 >> >> That's obviously not how it is, but I feel we should focus our attention >> on fixing this properly. >>> > > I think you did a typo there. There are 2 portage options > --rebuild-if-new-ver and --rebuild-if-new-rev. I opted for the *-ver > (version), since most revisions would not need to trigger a rebuild. > But the failure in that bug should be the same or similar fix to our > needs.
Not sure how *I* did a typo, looks like I typed the command properly above, and I've not even commented on the bug yet... Yeah I do realize that the bug is talking about -rev not -ver but the affected code appears to be shared hence why it's brought up. > >> As a rule, we don't want to hack around limitations in portage to make >> catalyst work. The toolchain team seems to have made it very clear they >> aren't updating to eapi5 soon, but the portage team has been fixing >> things left and right based on little more than my whims, I'd give them >> a chance to fix this before throwing hacks into catalyst to work around >> limitations in the package manager. >> >> Thanks, >> Zero >>> > > If someone wants to work on fixing it. The solution will require > extracting the NEEDED.ELF.2 info from the binpkg and confirming that the > links exist. If any of them don't, then trigger the build from source. > Rejecting the existing binpkg. > > You may also want to talk to blueness, he created a utility for looking > for broken elf links. Here is where I admit to being lazy, I was planning on "fixing" it by just triggering the src build no matter what when a rebuild occurs and then hoping that someday people in gentoo actually use EAPI5 and make this all unnecessary. - -Zero > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRpQuJAAoJEKXdFCfdEflKtI8P/iNpLeHAKD6E8li0hm2Pw5RI CM0HfvYmLioKdevAvlbvMjNiI/WgwgmOuF8Stj8biFZn80vYQpDYwuei6jEvnuSO wTBNmnI+v6kC91rVb7LTdpIOXpfCg3V27kHRNOWqNnyVSd4WK6kKjp6c2YqHcnwl 2bxHFjvOXFK8s/n9PVrBBgn5VrMqQzlc4VqVPn5FHQJP2/aMBpVChwrAZBcS6nGI 8wMVYMMfjwypk8jdroSTQC32Etw/T1jwcWPvUhgqtU7BCmGRSC1zXu22RuwfiLmK WPd2BmMl2jqBo6FOPSx83JfN+/OKumJy55aiz7LMVF+STPIfsSuzvvcipDJV2inv s8mkVXybpSYs/fdbpUEcx2fRuAeseSTAf96iMVVpjcKeFEavMxWzTSOwwQqFOkIy m8Gy8zON0YbpNZA/Zy5FnChYJ0R7ci8s0keEeVozMqE82XfgyAlkJFW771XQUs26 T+bK8sDgpANRxPx4c8AT18+Sudkplo7u06kDsRkQ+Ru2Plc9lsVYkpbI1FjjwG7X uxCjiigCZA5Y+x4tnoDo6Rl8rAhllRTuHbzZpjbvZXxFlYHgrMsSQzPNgwW7UqgC iIIYCd6rVrfSsc2qtgedJacdMYHTTGGy+Hq1SWNHWqsedhd063q4HJ3Wqk6Epivu nAtvVC7SFo/f++WU36+z =2knI -----END PGP SIGNATURE-----
