| 1 |
On Monday 13 June 2005 19:18, Robin H. Johnson wrote: |
| 2 |
> The bug hit me while working with GLI last night, and now I really do |
| 3 |
> need a solution for it. Looking at the dep tree to see why perl pulls |
| 4 |
> in openssl, the critical parts of the tree are this: |
| 5 |
> |
| 6 |
> (Trimmed to make things shorter) |
| 7 |
> [ebuild N ] dev-lang/perl-5.8.6-r4 +berkdb |
| 8 |
> [ebuild N ] sys-libs/db-4.2.52_p2 +java |
| 9 |
> [ebuild N ] dev-java/blackdown-jdk-1.4.2.01-r2 |
| 10 |
> (glibc, gcc, gcc-config, portage) |
| 11 |
> [ebuild N ] dev-lang/python-2.4.1 +berkdb +ssl |
| 12 |
> [ebuild N ] dev-libs/openssl-0.9.7g |
| 13 |
> |
| 14 |
> This suggests the following solutions: |
| 15 |
> 1. split berkdb support out of perl. |
| 16 |
> 2. split ssl support out of python. |
| 17 |
> 3. split java support out of db. |
| 18 |
> |
| 19 |
> #1 may be possible with mcumming's minimal perl (untested by me) |
| 20 |
> #2 appears to work (tested via package.use having 'python -ssl', and |
| 21 |
> looking at 'emerge -e -p system') #3 appears to work (tested via |
| 22 |
> package.use having 'db -java', and looking at 'emerge -e -p system') |
| 23 |
> |
| 24 |
> I tried implementing #3, but the ebuild work involved is very messy, and |
| 25 |
> non-ideal, as a large part of db is then built twice. |
| 26 |
> |
| 27 |
> Could the python and perl folk please comment here on the possibility of |
| 28 |
> moving those chunks (berkdb/ssl) of their packages to seperate packages? |
| 29 |
|
| 30 |
What I wonderis why blackdown-jdk (or any other jdk) actually depends on |
| 31 |
python. These jdk's are binary only packages that have no buildtime |
| 32 |
dependencies. The only source of the python dependency is java-config. In any |
| 33 |
case python should be a system package. |
| 34 |
|
| 35 |
Paul |
| 36 |
|
| 37 |
-- |
| 38 |
Paul de Vrieze |
| 39 |
Gentoo Developer |
| 40 |
Mail: pauldv@g.o |
| 41 |
Homepage: http://www.devrieze.net |
Archives