* kashani <kashani-l...@badapple.net>: > When building bugzilla-3.4.1-r1 which requires ~x86 I have to > unmask a number of perl modules. Two of those modules, listed above, > attempt to pull in perl-5.10.1 which isn't in portage. Hardmasking > packages that require dependencies that don't exist makes sense. If > you'd like to explain otherwise a little more data other than "cause > I said so" is required.
Let's have a look at the ebuild: > kash...@www01 /usr/portage/dev-lang/perl $ cat > /usr/portage/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild > # Copyright 1999-2009 Gentoo Foundation > # Distributed under the terms of the GNU General Public License v2 > # $Header: > /var/cvsroot/gentoo-x86/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild,v > 1.2 2009/08/25 10:56:52 tove Exp $ > > DESCRIPTION="Virtual for Test-Harness" > HOMEPAGE="http://www.gentoo.org/proj/en/perl/"; > SRC_URI="" > > LICENSE="GPL-2" > SLOT="0" > KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 > ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd" > IUSE="" > > DEPEND="" > RDEPEND="|| ( ~dev-lang/perl-5.10.1 ~perl-core/Test-Harness-${PV} )" The ebuild depends on dev-lang/perl-5.10.1 or perl-core/Test-Harness-3.17. The second one is in the tree so there is no need for hardmasking. So if you add virtual/perl-Test-Harness to package.keywords you should also add perl-core/Test-Harness. If you wonder why portage doesn't report both possibilities, visit the bugs in my other mail in this thread. Thanks
