From: "C. Brewer" <cbrewer@stealthaccess.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] db questions
Date: Mon, 20 Oct 2003 00:25:28 +0000 [thread overview]
Message-ID: <200310200025.43412.cbrewer@stealthaccess.net> (raw)
In-Reply-To: <20031020071009.GA19061@curie-int.orbis-terrarum.net>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1201 bytes --]
I was mistaken, there are only four installed. I was somewhat aware of the
why, but my concern lay in qpkg's lies:
# qpkg -q -I -nc db
sys-libs/db-3.2.9-r6
DEPENDED ON BY:
perl-5.8.1-r2
python-2.2.3-r3
postfix-2.0.16-r1
libperl-5.8.1
sys-libs/db-1.85-r1
DEPENDED ON BY:
perl-5.8.1-r2
python-2.2.3-r3
postfix-2.0.16-r1
libperl-5.8.1
sys-libs/db-4.0.14-r2
DEPENDED ON BY:
perl-5.8.1-r2
python-2.2.3-r3
postfix-2.0.16-r1
libperl-5.8.1
sys-libs/db-4.1.25_p1-r2
DEPENDED ON BY:
perl-5.8.1-r2
python-2.2.3-r3
postfix-2.0.16-r1
libperl-5.8.1
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?
--
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-20 7:25 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 [this message]
2003-10-20 11:00 ` Robin H. Johnson
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=200310200025.43412.cbrewer@stealthaccess.net \
--to=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