From: "Robin H. Johnson" <robbat2@gentoo.org>
To: "C. Brewer" <cbrewer@stealthaccess.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] db questions
Date: Mon, 20 Oct 2003 04:00:48 -0700 [thread overview]
Message-ID: <20031020110048.GC25165@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <200310200025.43412.cbrewer@stealthaccess.net>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Mon, Oct 20, 2003 at 12:25:28AM +0000, C. Brewer wrote:
I suspect qpkg isn't telling the truth more than anything else.
perl-5.8.1-r2
WANTS: sys-libs/db
python-2.2.3-r3
WANTS: >=sys-libs/db-3
postfix-2.0.16-r1
WANTS: >=sys-libs/db-3.2
libperl-5.8.1
WANTS: sys-libs/db
> sys-libs/db-1.85-r1
> sys-libs/db-3.2.9-r6
> sys-libs/db-4.0.14-r2
> sys-libs/db-4.1.25_p1-r2
Yeah, that's the most current of the lot.
Try 'emerge -epD world' and pipe that to a file, then see which versions
of db-3
> IIRC, these four, which represents the sum of stuff I have linked to db, call
> for db3 in the ebuilds. I dont mind testing the new, if something I used
> linked to it, and I am used to seeing at least the two copies that have been
> haunting for awhile(db1.85 and db3), but would it be possible to find out
> truthfully what is actually linked and to unmerge/mask/crucify the others?
blame qpkg. somebody was going to rewrite it i hear.
--
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: 232 bytes --]
prev parent reply other threads:[~2003-10-20 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 23:51 [gentoo-dev] db questions C. Brewer
2003-10-20 7:10 ` Robin H. Johnson
2003-10-20 0:25 ` C. Brewer
2003-10-20 11:00 ` Robin H. Johnson [this message]
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=20031020110048.GC25165@curie-int.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=cbrewer@stealthaccess.net \
--cc=gentoo-dev@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