public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ciaran.mccreesh@googlemail.com
Subject: Re: [gentoo-dev] Are tags just sets?
Date: Sun, 26 Jun 2011 10:54:44 +0200	[thread overview]
Message-ID: <20110626105444.366222bf@pomiocik.lan> (raw)
In-Reply-To: <20110626094341.30e1f043@googlemail.com>

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

On Sun, 26 Jun 2011 09:43:41 +0100
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:

> On Sun, 26 Jun 2011 10:41:24 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
> > A 'type' field would be useful as well, to support various kinds of
> > package sets (much like portage handles currently).
> 
> I'm highly doubtful that there's any real need for different kinds of
> repository-provided sets. We especially don't want sets to be code...

Simple things like getting a list of packages which own a particular
file (for rebuilds) or grepping a variable are useful to users.
For example, the x11 overlay provides a set to rebuild the xorg server
modules after an update.

> > We'd either want to add || ( ) here, or somehow explicitly specify
> > that this is a one-of set.
> 
> No, that's something that's determined by how the set's used, not by
> what's in the set. There's no such thing as a "one-of" set; a set is
> just a list of package dep specs.

Hm, true. I guess noone will want to merge 'a random package matching
a tag' :P.

-- 
Best regards,
Michał Górny

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

  reply	other threads:[~2011-06-26  8:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26  7:02 [gentoo-dev] Are tags just sets? Ciaran McCreesh
2011-06-26  8:41 ` Michał Górny
2011-06-26  8:43   ` Ciaran McCreesh
2011-06-26  8:54     ` Michał Górny [this message]
2011-06-26  9:00       ` Ciaran McCreesh
2011-06-26 12:48         ` Michał Górny
2011-06-27  5:51           ` Ciaran McCreesh
2011-06-26 11:33 ` Wyatt Epp
2011-06-26 12:17 ` Kent Fredric
2011-06-26 14:40 ` [gentoo-dev] " Duncan
2011-06-26 15:12 ` [gentoo-dev] " Maciej Mrozowski
2011-06-26 18:42   ` Kent Fredric
2011-06-27  5:49   ` Ciaran McCreesh
2011-06-27 18:21     ` Maciej Mrozowski
2011-06-28  6:19       ` Ciaran McCreesh
2011-06-27 20:23     ` Rich Freeman
2011-06-27 21:06       ` Wyatt Epp
2011-06-27 21:23         ` Rich Freeman
2011-06-27 21:39           ` Wyatt Epp
2011-06-28  6:19       ` Ciaran McCreesh
2011-06-28  3:26 ` Brian Harring
2011-06-28  3:43   ` Kent Fredric
2011-06-28  9:31     ` Brian Harring
2011-06-28 11:53   ` Peter Volkov
2011-06-28 15:33     ` Wyatt Epp
2011-06-28 18:52   ` Maciej Mrozowski

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=20110626105444.366222bf@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=ciaran.mccreesh@googlemail.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