From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Required Features for $package_manager to Aid... Development!
Date: Wed, 6 Sep 2006 04:05:30 -0700 [thread overview]
Message-ID: <20060906110529.GB27046@seldon> (raw)
In-Reply-To: <20060906102911.GD25413@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
On Wed, Sep 06, 2006 at 10:29:11AM +0000, Elfyn McBratney wrote:
> Hola,
>
> I've been inspired by the local/global USE flag threads recently
> posted by Doug (Cardoe), and it got me to thinking... I've recently
> joined the pkgcore development effort, and was asked by Brian
> (ferringb) what I'd like to hack on/what my niggles with portage are.
> My personal one is why updates/ and binpkg mangling takes so long in
> portage-$current. But I'd like to know, what are everyone elses?
>
> I know that this topic have been rehashed since the dawn of
> time^Wgentoo-dev, but these things get lost, opinions change... and
> since last year, new and viable alternate package managers have
> cropped up. So, basically I'd like to ask all on this list: - what
> package manager features would make *your* life easier?
>
> Personally, I'd like to see the following groups of changes happen one
> way or another:
>
> * Improve QA with/by:
> - Detecting conflicting USE flags;
That one is on the map for trying to address via eapi=1; intention was
to resurrect the approach of using a seperate metadata key, and
extending depset support to include xor so that representing the
_valid_ use conditional states is possible.
Simple example, if you need mysql or postgres, but not both;
VALID_USE_STATES="^ ( mysql postgres )"
if it's not required to have them enabled, but still need one or the
other if enabled
VALID_USE_STATES="( || ( mysql postgres ) ^ ( mysql postgres ) )"
Would need to extend depset in this case to support negation of blocks
also (nand/nor); downside, it gets verbose.
Upshot, it uses extisting syntax folks are familar with; the verbosity
of it would also go down if/when use groups were implemented thus
replacing USE_EXPAND (something that needs resurrecting and is another
bit on the map, although not guranteed to be targeted).
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-06 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 10:29 [gentoo-dev] [RFC] Required Features for $package_manager to Aid... Development! Elfyn McBratney
2006-09-06 11:05 ` Brian Harring [this message]
2006-09-07 3:19 ` [gentoo-dev] " Ryan Hill
2006-09-09 13:37 ` Chris Gianelloni
2006-09-09 21:17 ` S. Lockwood-Childs
2006-09-09 22:06 ` Mike Frysinger
2006-09-10 3:57 ` Alec Warner
2006-09-10 14:57 ` Francesco Riosa
2006-09-09 22:05 ` Mike Frysinger
2006-09-09 23:27 ` [gentoo-dev] " Luca Barbato
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=20060906110529.GB27046@seldon \
--to=ferringb@gmail.com \
--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