public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] VDB access
Date: Wed, 6 Feb 2008 17:14:02 +0000	[thread overview]
Message-ID: <20080206171402.18210c34@snowcone> (raw)
In-Reply-To: <47A8D35E.4030708@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

On Tue, 05 Feb 2008 13:21:34 -0800
Zac Medico <zmedico@gentoo.org> wrote:
> > * Allow package managers that implement native_built_with_use to
> > sandbox off vdb completely, and ban all ebuild access to vdb.
> 
> The problem that I see with native_built_with_use is that the
> package manager will then need to precisely implement the
> build_with_use interface along with any and all supported options
> (and this interface would effectively become part of the EAPI).

True.

> If the package manager exposes a slightly lower level interface to
> the USE flags then build_with_use can use that instead, and the
> package manager won't have to implement the full build_with_use
> interface.  For example, portageq currently supports a "metadata"
> command that can be used to query installed package metadata such as
> USE and IUSE. Perhaps we should use some type of interface similar
> to that.

That's also a possibility. How about something like:

if [[ -n "${E_INSTALLED_PKG_METADATA_CMD}" ]] ; then
    ${E_INSTALLED_PKG_METADATA_CMD} >=cat/pkg-1.23 USE foo
else
    # old vdb stuff
fi

with heavy (and checked) restrictions upon legal metadata keys (stuff
that's in individual files, not environment.bz2)?

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-02-06 17:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  1:05 [gentoo-dev] VDB access Ciaran McCreesh
2008-02-05  7:43 ` [gentoo-dev] " 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 [this message]
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=20080206171402.18210c34@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