On Tue, 2005-06-14 at 22:50 +0200, Paul de Vrieze wrote: > On Monday 13 June 2005 19:18, Robin H. Johnson wrote: > > The bug hit me while working with GLI last night, and now I really do > > need a solution for it. Looking at the dep tree to see why perl pulls > > in openssl, the critical parts of the tree are this: > > > > (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 > > > > This suggests the following solutions: > > 1. split berkdb support out of perl. > > 2. split ssl support out of python. > > 3. split java support out of db. > > > > #1 may be possible with mcumming's minimal perl (untested by me) > > #2 appears to work (tested via package.use having 'python -ssl', and > > looking at 'emerge -e -p system') #3 appears to work (tested via > > package.use having 'db -java', and looking at 'emerge -e -p system') > > > > I tried implementing #3, but the ebuild work involved is very messy, and > > non-ideal, as a large part of db is then built twice. > > > > Could the python and perl folk please comment here on the possibility of > > moving those chunks (berkdb/ssl) of their packages to seperate packages? > > 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.
That and java is not enabled on any of the profiles I have been working with, so that isn't the issue when we are building stages. -- Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
