| 1 |
On Tue, Jun 14, 2005 at 10:50:05PM +0200, Paul de Vrieze wrote: |
| 2 |
> > (Trimmed to make things shorter) |
| 3 |
> > [ebuild N ] dev-lang/perl-5.8.6-r4 +berkdb |
| 4 |
> > [ebuild N ] sys-libs/db-4.2.52_p2 +java |
| 5 |
> > [ebuild N ] dev-java/blackdown-jdk-1.4.2.01-r2 |
| 6 |
> > (glibc, gcc, gcc-config, portage) |
| 7 |
> > [ebuild N ] dev-lang/python-2.4.1 +berkdb +ssl |
| 8 |
> > [ebuild N ] dev-libs/openssl-0.9.7g |
| 9 |
> What I wonderis why blackdown-jdk (or any other jdk) actually depends on |
| 10 |
> python. These jdk's are binary only packages that have no buildtime |
| 11 |
> dependencies. The only source of the python dependency is java-config. In any |
| 12 |
> case python should be a system package. |
| 13 |
java-config only has a RDEPEND on python. |
| 14 |
|
| 15 |
The stage2 command is 'emerge -e system'. |
| 16 |
|
| 17 |
blackdown-jdk DEPEND="virtual/libc" |
| 18 |
glibc DEPEND="sys-devel/gcc" |
| 19 |
gcc DEPEND="sys-devel/gcc-config" |
| 20 |
- Maybe this should be an RDEPEND only? |
| 21 |
gcc-config DEPEND="sys-devel/portage" |
| 22 |
- Maybe this should be an RDEPEND only? |
| 23 |
portage RDEPEND="dev-lang/python" |
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Robin Hugh Johnson |
| 30 |
E-Mail : robbat2@××××××××××××××.net |
| 31 |
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 |
| 32 |
ICQ# : 30269588 or 41961639 |
| 33 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives