On Fri, Jun 24, 2011 at 02:51, Ciaran McCreesh
> If you abolish categories in favour of tags, but tags don't uniquely
> identify a package, how do you uniquely identify a package?
> Remember that your solution has to work with overlays and with tags
> being changed after a package is installed.
I seem to have misunderstood the thrust of your question? media-sound
is a category (tag); each package still has its name, URI, files
associated with it and their checksums. A combination of a tag or two
and package name is going to be plenty for such a small data set
excepting some pretty absurd circumstance where four projects all
choose the same name and do the same thing. Alternatively, we could
just make names unique in the first place and nip that problem in the
bud forever. Either way, tags changing isn't especially different
from categories changing.
On Fri, Jun 24, 2011 at 03:18, Zac Medico <firstname.lastname@example.org> wrote:
> On 06/23/2011 05:07 PM, Wyatt Epp wrote:
> Since categories and tags can easily coexist, you might want to rethink
> that. It's relatively easy to implement a tagging mechanism, while
> (unnecessarily) ripping out the existing category framework is a big
> chore that may not have any practical value.
I was more thinking that in the long term it's reduplication of effort
and annoying. I probably should have worded it as "tags deprecate
categories". You're right that practically speaking, once we figure
out where to put it, it's roughly within reach.