From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] VDB access
Date: Tue, 5 Feb 2008 01:05:46 +0000 [thread overview]
Message-ID: <20080205010546.38414ec3@snowcone> (raw)
The following things access VDB by hand:
* gnome2-utils.eclass. Will be fixed once a portage with proper
env saving goes stable, which isn't too far off. Bug 155993.
* net-misc/l7-filter. This can be fixed as soon as portage with proper
env saving goes stable.
* kde.eclass, for slot_rebuild. This seems like it's a really dumb hack
to cater for users who don't know how to use revdep-rebuild (there
seems to be a lot of that going around, making elog worthless, but
that's a different issue...), and should probably just be removed.
* pcmcia.eclass. Supposedly deprecated. Bug 140289.
* eutils.eclass. For built_with_use.
Of these, only the last appears to be of any use. So how about the
following?
* Modify built_with_use so that it calls native_built_with_use if such
a function exists, and falls back to its own implementation otherwise.
* Allow package managers that implement native_built_with_use to sandbox
off vdb completely, and ban all ebuild access to vdb.
This will let package managers use a format other than VDB. A well
designed replacement can shave a minute off cold cache command times.
--
Ciaran McCreesh
--
gentoo-dev@lists.gentoo.org mailing list
next reply other threads:[~2008-02-05 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 1:05 Ciaran McCreesh [this message]
2008-02-05 7:43 ` [gentoo-dev] Re: VDB access Christian Faulhammer
2008-02-05 19:02 ` Ciaran McCreesh
2008-02-06 6:43 ` Petteri Räty
2008-02-06 17:09 ` Ciaran McCreesh
2008-02-05 21:21 ` [gentoo-dev] " Zac Medico
2008-02-06 6:30 ` Vlastimil Babka
2008-02-06 7:49 ` Zac Medico
2008-02-06 13:24 ` Michael Haubenwallner
2008-02-06 18:16 ` Ciaran McCreesh
2008-02-06 17:14 ` Ciaran McCreesh
2008-02-07 7:41 ` Zac Medico
2008-02-08 9:54 ` Ciaran McCreesh
2008-04-10 8:07 ` Rémi Cardona
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=20080205010546.38414ec3@snowcone \
--to=ciaran.mccreesh@blueyonder.co.uk \
--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