| Summary: | Portage 2.0.50-r1 ebuild does unnecesairy rebuild of sandbox. | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Ronald Hummelink <ronald> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | vapier |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** Bug 63628 has been marked as a duplicate of this bug. *** 2.0.51 resolves this |
During src_compile() sandbox is build (on x86 with special CFLAGS even) if [ "${ARCH}" = "x86" ]; then make CFLAGS="-march=i386 -O1 -pipe" || die else make || die fi During src_install() it is make cleaned and rebuild, without exception for x86 #install sandbox cd ${S}/src/sandbox-1.1 make clean make DESTDIR=${D} install || die "Failed to compile sandbox" Now all seems to work fine, so it is really a matter of pointing out the inconsistency... The make clean seems to have been added in the 2.0.50 series. Also it is useless to build it twice, but yet again since this is so fast it is trivial.