| Summary: | app-emulation/mol minor fix | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Maurizio Disimino <kevin> |
| Component: | New packages | Assignee: | Kevyn Shortell (RETIRED) <trance> |
| Status: | VERIFIED FIXED | ||
| Severity: | minor | CC: | mguertin |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
same for sys-apps/yaboot sys-apps/gtkpbbuttons
sys-apps/hfsplusutils
sys-apps/hfsutils
sys-apps/pbbuttonsd
sys-apps/powerpc-utils
sys-apps/powerprefs
Moreover:
(from gentoo.org/~karltk/POLICY.txt)
If you do not know if an ebuild will work on a partiticular
profile, leave that keyword out. If you know a that a package
will not work on a particular profile, add that keyword with a
leading "-" to KEYWORDS.
eg: ppc-sources would have: KEYWORDS="ppc -x86 -sparc -sparc64"
sexybit portage # grep KEYWORD
sys-apps/{hfsplusutils,pbbuttonsd,hfsutils,gtkpbbuttons,powerprefs}/*.ebuild
sys-apps/hfsplusutils/hfsplusutils-1.0.4.ebuild:KEYWORDS="ppc"
sys-apps/pbbuttonsd/pbbuttonsd-0.4.10.ebuild:KEYWORDS="ppc"
sys-apps/pbbuttonsd/pbbuttonsd-0.4.10a.ebuild:KEYWORDS="ppc"
sys-apps/hfsutils/hfsutils-3.2.6.ebuild:KEYWORDS="ppc"
sys-apps/gtkpbbuttons/gtkpbbuttons-0.4.6b.ebuild:KEYWORDS="ppc"
sys-apps/powerprefs/powerprefs-0.2.1.ebuild:KEYWORDS="ppc"
sys-apps/powerprefs/powerprefs-0.2.ebuild:KEYWORDS="ppc"
Hmm I thought I added those keywords to those builds (all the - ones).. I will add them now I guess. done and comitted.
grep KEYWORD
sys-apps/{hfsplusutils,pbbuttonsd,hfsutils,gtkpbbuttons,powerprefs}/*.ebuild
sys-apps/hfsplusutils/hfsplusutils-1.0.4.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
sys-apps/pbbuttonsd/pbbuttonsd-0.4.10.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
sys-apps/pbbuttonsd/pbbuttonsd-0.4.10a.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
sys-apps/hfsutils/hfsutils-3.2.6.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
sys-apps/gtkpbbuttons/gtkpbbuttons-0.4.6b.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
sys-apps/powerprefs/powerprefs-0.2.1.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
sys-apps/powerprefs/powerprefs-0.2.ebuild:KEYWORDS="ppc -x86 -sparc -sparc64"
Verified, closing |
from app-emulation/mol: <snip> KEYWORDS="ppc -x86 -sparc -sparc64" pkg_setup() { if [ ${ARCH} != "ppc" ] ; then eerror "Sorry, this is a PPC only package." die "Sorry, this as a PPC only pacakge." fi } </snip> well, assuming this pkg is 'keyword masked' for ARCH != ppc that pkg_setup() stuff is there only for backward compatibility (i.e. old portage versions) @<Gerk> j2ee: if you are running older portage and are on non ppc that is only way it stops you from installing +<j2ee> Gerk: ack, allright then @<Gerk> j2ee: I know its kinda ugly tho.. but it doesnt breakanything ;) @<Gerk> j2ee: I was actually asked to put that stuff in the ppc only pkgs at one point +<j2ee> indeed @<Gerk> if you wanna file a bug to have it profile masked on all non ppc profiles thats coolw with me too @<Gerk> and once it is I'll remove that stuff ;) @<Gerk> that means all x86 and sparc profiles though ;)