From: Andrew Gaffney <agaffney@skylineaero.com>
To: Brian Harring <ferringb@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] format of files in /var/cache/edb/dep
Date: Fri, 14 May 2004 11:25:32 -0500 [thread overview]
Message-ID: <40A4F2FC.8070803@skylineaero.com> (raw)
In-Reply-To: <9B984328-A5C3-11D8-87FF-000A95C08860@gentoo.org>
Brian Harring wrote:
>
> On May 13, 2004, at 8:33 PM, Andrew Gaffney wrote:
>
>>> I've looked around for a reference to the format of the files in
>>> /var/cache/edb/dep, but I can't seem to find anything. From looking at
>>> /var/cache/edb/dep/x11-base/xfree-4.3.0-r5, it seems that it is:
>>>
>>> DEPEND
>>> RDEPEND
>>> SLOT
>>> SRC_URI
>>> RESTRICT
>>> HOMEPAGE
>>> LICENSE
>>> DESCRIPTION
>>> KEYWORDS
>>> ?
>>> IUSE
>>> ?
>>> ?
>>>
>>> Can someone verify what I have filled in and fill in my blanks? Thank
>>> you.
>
> You're after the auxdbkeys list in portage.py- this is it, note that the
> flatfile cache's use the same ordering for storage-
> auxdbkeys=[
> 'DEPEND',
> 'RDEPEND',
> 'SLOT',
> 'SRC_URI',
> 'RESTRICT',
> 'HOMEPAGE',
> 'LICENSE',
> 'DESCRIPTION',
> 'KEYWORDS',
> 'INHERITED',
> 'IUSE',
> 'CDEPEND',
> 'PDEPEND',
> 'PROVIDE',
> 'UNUSED_01',
> 'UNUSED_02',
> 'UNUSED_03',
> 'UNUSED_04',
> 'UNUSED_05',
> 'UNUSED_06',
> 'UNUSED_07',
> 'UNUSED_08'
> ]
>
> (pull from portage-2.0.51_pre7)
> ~brian
Thanks. That's just what I needed. Someone also suggested to look at the end of
ebuild.sh, which contains about the same information.
--
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-05-14 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 1:33 [gentoo-dev] format of files in /var/cache/edb/dep Andrew Gaffney
2004-05-14 1:43 ` Ciaran McCreesh
2004-05-14 2:19 ` Andrew Gaffney
2004-05-14 2:30 ` Mike Frysinger
2004-05-14 2:37 ` Andrew Gaffney
2004-05-14 16:27 ` Brian Harring
2004-05-14 16:25 ` Andrew Gaffney [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=40A4F2FC.8070803@skylineaero.com \
--to=agaffney@skylineaero.com \
--cc=ferringb@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