Summary: | sys-libs/glibc downgrade check in pkg_setup should use MERGE_TYPE (to support `emerge -B`) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Phil White <cerise-gentoo> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Phil White
2009-01-15 23:24:08 UTC
most people who downgrade do it because they want to downgrade, not because they want to test compile if you want to test compile, dont run the setup step: ebuild <glibc ebuild> clean unpack compile install Not 'test compile'. I'm talking about building a package for another system. By not fixing this, you are preventing anyone from setting up a standard build system for potentially more than one platform. Is there a reason that moving that check would break something or cause an undesirable effect? unless there's a way to detect portage is doing -B, then you'll have to work around the issue by doing: ROOT=// emerge sys-libs/glibc -B i told you why it's undesirable: people would waste time building an entire glibc (which is not fast) only to have it call die Maybe an ewarn message in pkg_setup would be sufficient, with the die to pkg_preinst. There's currently no clues in the environment for the ebuild to determine that it's executing in --buildpkgonly mode. We can add an EAPI extension for that, similar to bug 154495. once we update glibc to a newer EAPI, we can fix this i've added the check, but it won't really start working until the EAPI is updated. but that's being done elsewhere. Commit message: Check MERGE_TYPE when doing downgrade check http://sources.gentoo.org/sys-libs/glibc/files/eblits/pkg_setup.eblit?r1=1.11&r2=1.12 |