From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why is dev-db/edb needed by imlib2?
Date: Mon, 20 Oct 2003 02:05:09 -0400 [thread overview]
Message-ID: <200310200205.10408.vapier@gentoo.org> (raw)
In-Reply-To: <20031019053404.GB7412@miyazaki>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 538 bytes --]
On Sunday 19 October 2003 01:34, Kain wrote:
> IIRC edb is the image collection format used in the E17 programs, so if you
> are running the e17 devel code, than whatever imlib2 your e17 code links
> into will need edb enabled.
from the enlightenment page:
This is a database library based on Berkeley DB 2.7.7 from http://
www.sleepycat.com. It is intended to make accessing database information
portable, easy, fast and efficient.
if any e17 components need it, i have it listed in DEPEND, so thats not a
problem
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2003-10-20 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 23:31 [gentoo-dev] Why is dev-db/edb needed by imlib2? Peter Ruskin
2003-10-19 1:08 ` Mike Frysinger
2003-10-19 1:46 ` Peter Ruskin
2003-10-19 5:34 ` Kain
2003-10-20 6:05 ` Mike Frysinger [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=200310200205.10408.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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