From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] perl/openssl circular dep, possible solution (python/perl/db devs please read)
Date: Mon, 13 Jun 2005 10:18:29 -0700 [thread overview]
Message-ID: <20050613171829.GA25427@curie-int.orbis-terrarum.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
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?
--
Robin Hugh Johnson
E-Mail : robbat2@orbis-terrarum.net
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
[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]
next reply other threads:[~2005-06-13 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 17:18 Robin H. Johnson [this message]
2005-06-13 18:13 ` [gentoo-dev] perl/openssl circular dep, possible solution (python/perl/db devs please read) Michael Cummings
2005-06-13 18:47 ` Lars Weiler
2005-06-13 23:57 ` Danny van Dyk
2005-06-14 20:50 ` Paul de Vrieze
2005-06-14 21:15 ` Robin H. Johnson
2005-06-14 21:32 ` Paul de Vrieze
2005-06-14 21:48 ` Mike Frysinger
2005-06-15 13:45 ` Chris Gianelloni
2005-06-15 14:34 ` Mike Frysinger
2005-06-15 15:20 ` Chris Gianelloni
2005-06-14 22:52 ` Marius Mauch
2005-06-14 22:51 ` Mike Frysinger
2005-06-15 9:39 ` Michael Cummings
2005-06-15 9:26 ` Paul de Vrieze
2005-06-15 15:24 ` Marius Mauch
2005-06-15 13:38 ` Chris Gianelloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050613171829.GA25427@curie-int.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox