public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Are tags just sets?
Date: Tue, 28 Jun 2011 07:19:11 +0100	[thread overview]
Message-ID: <20110628071911.65eb9143@googlemail.com> (raw)
In-Reply-To: <BANLkTimcFUrh8PFUqR+CJq_yM9AMtaGswQ@mail.gmail.com>

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

On Mon, 27 Jun 2011 16:23:54 -0400
Rich Freeman <rich0@gentoo.org> wrote:
> Sets should really be something carefully controlled by the
> repository.  While I'm fine with having tags in the repository also,
> there is talk about giving users ways of supplying them as well.

Why? You can have carefully controlled sets for fancy things. But tag
sets don't need to be carefully controlled.

The way you give users control over tags using sets is to make sets in
overlays be merged with sets with the same name in the main tree, and
then allow users who feel like it to publish an overlay containing
their tags.

> Here is how I see tags being used:
> 
> 1.  I want a WYSIWYG html editor.
> 2.  I search for tags like "editor" and "html" and "WYSIWYG" and maybe
> even "text."
> 3.  I check out descriptions and homepages or whatever for a few
> likely candidates, and install one or maybe two.

$package_mangler search-tags editor html wysywig

> What I doubt I'd ever do is just install any package that has anything
> to do with text/html editing.

Not really a problem. Sets are usable for lots of things, not just
installing. They're useful in configuration files, for example -- you'd
probably never want to install every X driver either, but you might
want to set some options for every X driver.

-- 
Ciaran McCreesh

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

  parent reply	other threads:[~2011-06-28  6:23 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
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 [this message]
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=20110628071911.65eb9143@googlemail.com \
    --to=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