Summary: | 2.0.50-r2 causes some : dependency expressions to fail | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Johan Backlund <johan> |
Component: | Core - Dependencies | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amd64, dev-portage, sutherla |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Johan Backlund
2004-03-22 14:16:01 UTC
actually that's a bug in the evolution ebuild ... the proper syntax is as you showed, !amd64? ( stuff ) Then 2.0.50-r2 has been made more strict than r1? I find the evolution syntax quite logical, so then I should suggest that it is allowed as before. find /usr/portage -name "*.ebuild" | xargs grep '([ \t]* )[ \t]*:' shows that the same syntax occurs in evolution 1.4.5 as well as a couple of samba-3 ebuilds. amd64? ( ) : ( kerberos? ( >=app-crypt/mit-krb5-1.2.5 ) ) that may be logical, but the 2nd version is def _much_ more readable (especially for a newcomer) *** Bug 45447 has been marked as a duplicate of this bug. *** don't know how that got into there ... /me looks at amd64 people fixed to use the second syntax. if you want amd64 ppl to look, cc them. amd64 ppl, check this bug out. I think Brad added it. Anyway, kerberos is available on amd64 now, so I just fixed both evolution and samba to totally drop the !amd64 deps. |