public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Are tags just sets?
Date: Mon, 27 Jun 2011 16:23:54 -0400	[thread overview]
Message-ID: <BANLkTimcFUrh8PFUqR+CJq_yM9AMtaGswQ@mail.gmail.com> (raw)
In-Reply-To: <20110627064924.499c488c@googlemail.com>

On Mon, Jun 27, 2011 at 1:49 AM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Sun, 26 Jun 2011 17:12:27 +0200
> Maciej Mrozowski <reavertm@gmail.com> wrote:
>
>> Sets concept is completely orthogonal to tags concept, please do not
>> mix unrelated things.
>
> Depends upon what you think the "tags concept" is. We've already
> established that everyone has a different idea of what tags are anyway.

I too feel that tags should be distinct from sets, for a bunch of reasons.

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.

Sets are generally used to tell the package manager to do something
with a lot of packages at once.  I'm not sure there is much of a need
to do this with tags, at least not in most of the use cases that have
been suggested.

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.

What I doubt I'd ever do is just install any package that has anything
to do with text/html editing.  When you search google you care about
the top 5-10 - not the whole set of results.

Maybe if we define multiple namespaces for tags we could move to using
tags as dependencies or whatever, and those tags would be distinct and
much more carefully defined and controlled.  However, I think this is
more far-out and not the immediate goal.

Sets might work, but they seem a bit like a hack...

Rich



  parent reply	other threads:[~2011-06-27 20:24 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 [this message]
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=BANLkTimcFUrh8PFUqR+CJq_yM9AMtaGswQ@mail.gmail.com \
    --to=rich0@gentoo.org \
    --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