1 |
On 24 June 2011 20:14, Wyatt Epp <wyatt.epp@×××××.com> wrote: |
2 |
> On Fri, Jun 24, 2011 at 02:51, Ciaran McCreesh |
3 |
> <ciaran.mccreesh@××××××××××.com> wrote: |
4 |
>> If you abolish categories in favour of tags, but tags don't uniquely |
5 |
>> identify a package, how do you uniquely identify a package? |
6 |
>> |
7 |
>> Remember that your solution has to work with overlays and with tags |
8 |
>> being changed after a package is installed. |
9 |
>> |
10 |
> I seem to have misunderstood the thrust of your question? media-sound |
11 |
> is a category (tag); each package still has its name, URI, files |
12 |
> associated with it and their checksums. A combination of a tag or two |
13 |
> and package name is going to be plenty for such a small data set |
14 |
> excepting some pretty absurd circumstance where four projects all |
15 |
> choose the same name and do the same thing. Alternatively, we could |
16 |
> just make names unique in the first place and nip that problem in the |
17 |
> bud forever. Either way, tags changing isn't especially different |
18 |
> from categories changing. |
19 |
> |
20 |
|
21 |
Not really, after all, files will always have 1 canonical path, and |
22 |
all the other paths will be some form of reference to that canonical |
23 |
path ( ie: symlinks, a text-file with the canonical name, etc ) |
24 |
|
25 |
Tags would only be used for user access, not for internal dependency |
26 |
cycles, and internals would ultimately use the canonical path for the |
27 |
ebuild in sourcing the ebuild and generating the respective folder in |
28 |
the VDB. |
29 |
|
30 |
As it stands, when something changes category, many things must |
31 |
happen. All the things that depend on it must change, the package must |
32 |
be relocated in the VDB, and all the things that depend on it in the |
33 |
VDB need to be patched to refer to the newly located category name. |
34 |
|
35 |
With tags, I'd expect none of this neccessary, all that would change |
36 |
is the metadata index that maps tags to package names. |
37 |
|
38 |
> I was more thinking that in the long term it's reduplication of effort |
39 |
> and annoying. I probably should have worded it as "tags deprecate |
40 |
> categories". You're right that practically speaking, once we figure |
41 |
|
42 |
I myself can't see tags immediately replacing categories, not without |
43 |
needing to do something asinine like putting all the ebuilds in a |
44 |
top-level directory with no parent categories, named by SHA1 Sum, as |
45 |
the "Canonical pool" of packages which all the tag "references" point |
46 |
to. |
47 |
|
48 |
Moving to that state of things seems like a /long/ way off, if ever. |
49 |
|
50 |
|
51 |
-- |
52 |
Kent |
53 |
|
54 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
55 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |
56 |
|
57 |
http://kent-fredric.fox.geek.nz |