From: Brian Davis <bridavis@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Do you leave it on? USE="berkdb"
Date: Tue, 17 Oct 2006 10:53:18 -0400 [thread overview]
Message-ID: <4534EE5E.5090901@comcast.net> (raw)
In-Reply-To: <49bf44f10610161953k4db4f734ta0c7288ae9f4775e@mail.gmail.com>
I have mine off. However, you should see which packages you have
installed that would take advantage of it before you turn it off globally.
Grant wrote:
> Do you guys leave the berkdb USE flag on? It seems to be a default
> flag, but I've been using -berkdb in make.conf ever since I started
> using Gentoo. Is it basically a better way for lots of different
> packages to manage their databases?
>
> - Grant
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-17 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 2:53 [gentoo-user] Do you leave it on? USE="berkdb" Grant
2006-10-17 14:53 ` Brian Davis [this message]
2006-10-22 3:21 ` Grant
2006-10-22 9:55 ` kashani
2006-10-22 15:14 ` Grant
2006-10-22 17:04 ` [gentoo-user] " Harm Geerts
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=4534EE5E.5090901@comcast.net \
--to=bridavis@comcast.net \
--cc=gentoo-user@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