From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Are tags just sets?
Date: Mon, 27 Jun 2011 06:42:39 +1200 [thread overview]
Message-ID: <BANLkTimOJwhdfTvLcA+cUR8iE1qRd-Or=w@mail.gmail.com> (raw)
In-Reply-To: <201106261712.27665.reavertm@gmail.com>
On 27 June 2011 03:12, Maciej Mrozowski <reavertm@gmail.com> wrote:
>
> I see major disadvantage with this approach. It's painful to maintain.
> Imagine hundreds of different tags, with each package having at least two
> tags. You certainly don't expect anyone to be able to maintain that.
> Also those files cannot be generated since there needs to be some original
> source of tags information to generate such 'sets' from.
This problem is in my mind somewhat twofold.
There are 2 ways to approach applying a tag.
1. Opening each package and setting its tags ( package -> tags )
2. Opening a "tag" file and setting its packages ( tag -> package )
And both approaches are very handy.
1. Is useful because it makes it easy to apply a singular tag surgically.
2. Is useful because it makes it easy to apply one tag to a raft of packages.
However, if one wishes to implement something that works without
touching anything remotely part of portage itself, and one wants a
fast and easy proof of concept , number 2 is the preferable approach.
( Because you can make a basic example set of tags easily simply with
a bit of "find > file" for each tag you wish to create )
Ultimately I think we'll see both forms emerging, long term we'll
probably edit metadata.xml, and the data will be aggregated to form a
singular fast-to-read tag index for each tag.
But we can develop the other half of the system, the "Work with an
existing tag index of sorts" /now/ and get a working proof of concept
without needing to derail ourselves bikeshedding how the portage side
of things will work.
( And I think we can expect to see tools emerge for maintaining
package tags, whether it be surgically or low-orbit-ion-cannon grade
precision )
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
http://kent-fredric.fox.geek.nz
next prev parent reply other threads:[~2011-06-26 18:43 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 [this message]
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='BANLkTimOJwhdfTvLcA+cUR8iE1qRd-Or=w@mail.gmail.com' \
--to=kentfredric@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