On Tue, Jun 14, 2005 at 10:50:05PM +0200, Paul de Vrieze wrote: > > (Trimmed to make things shorter) > > [ebuild N ] dev-lang/perl-5.8.6-r4 +berkdb > > [ebuild N ] sys-libs/db-4.2.52_p2 +java > > [ebuild N ] dev-java/blackdown-jdk-1.4.2.01-r2 > > (glibc, gcc, gcc-config, portage) > > [ebuild N ] dev-lang/python-2.4.1 +berkdb +ssl > > [ebuild N ] dev-libs/openssl-0.9.7g > What I wonderis why blackdown-jdk (or any other jdk) actually depends on > python. These jdk's are binary only packages that have no buildtime > dependencies. The only source of the python dependency is java-config. In any > case python should be a system package. java-config only has a RDEPEND on python.
The stage2 command is 'emerge -e system'. blackdown-jdk DEPEND="virtual/libc" glibc DEPEND="sys-devel/gcc" gcc DEPEND="sys-devel/gcc-config" - Maybe this should be an RDEPEND only? gcc-config DEPEND="sys-devel/portage" - Maybe this should be an RDEPEND only? portage RDEPEND="dev-lang/python" -- Robin Hugh Johnson E-Mail : [EMAIL PROTECTED] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgpPS2V4vpHYk.pgp
Description: PGP signature
