1 |
On Tuesday 14 June 2005 23:15, Robin H. Johnson wrote: |
2 |
> On Tue, Jun 14, 2005 at 10:50:05PM +0200, Paul de Vrieze wrote: |
3 |
> > > (Trimmed to make things shorter) |
4 |
> > > [ebuild N ] dev-lang/perl-5.8.6-r4 +berkdb |
5 |
> > > [ebuild N ] sys-libs/db-4.2.52_p2 +java |
6 |
> > > [ebuild N ] dev-java/blackdown-jdk-1.4.2.01-r2 |
7 |
> > > (glibc, gcc, gcc-config, portage) |
8 |
> > > [ebuild N ] dev-lang/python-2.4.1 +berkdb +ssl |
9 |
> > > [ebuild N ] dev-libs/openssl-0.9.7g |
10 |
> > |
11 |
> > What I wonderis why blackdown-jdk (or any other jdk) actually depends on |
12 |
> > python. These jdk's are binary only packages that have no buildtime |
13 |
> > dependencies. The only source of the python dependency is java-config. In |
14 |
> > any case python should be a system package. |
15 |
> |
16 |
> java-config only has a RDEPEND on python. |
17 |
> |
18 |
> The stage2 command is 'emerge -e system'. |
19 |
> |
20 |
> blackdown-jdk DEPEND="virtual/libc" |
21 |
> glibc DEPEND="sys-devel/gcc" |
22 |
> gcc DEPEND="sys-devel/gcc-config" |
23 |
> - Maybe this should be an RDEPEND only? |
24 |
> gcc-config DEPEND="sys-devel/portage" |
25 |
|
26 |
I don't think gcc-config should depend on portage at all. Or does it actually |
27 |
use portage services. In any case it should be an RDEPEND, as building does |
28 |
not depend on portage being there. |
29 |
|
30 |
> - Maybe this should be an RDEPEND only? |
31 |
> portage RDEPEND="dev-lang/python" |
32 |
|
33 |
Portage does provide some very simple binary python modules. These depend at |
34 |
compiletime on python headers. Providing those headers separately might help |
35 |
though. Just as well as splitting out those modules. |
36 |
|
37 |
Paul |
38 |
|
39 |
-- |
40 |
Paul de Vrieze |
41 |
Gentoo Developer |
42 |
Mail: pauldv@g.o |
43 |
Homepage: http://www.devrieze.net |