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