| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Feb 8, 2008 7:32 AM, Donnie Berkholz wrote: |
| 5 |
> I don't think categories are the best way of resolving ambiguities, |
| 6 |
> because they don't uniquely identify a package. One could imagine two |
| 7 |
> packages in the same category with the same name (for example, two |
| 8 |
> Python modules that do drastically different things but would go in |
| 9 |
> dev-python). |
| 10 |
|
| 11 |
In my humble opinion, the current classification is perfectly fine in |
| 12 |
practice -- it is quite similar to the human naming system: |
| 13 |
|
| 14 |
, => / (okay, not exactly -- categs are limited -- but close enough) |
| 15 |
|
| 16 |
Surely there are more humans than packages, but we do fine don't we? :) |
| 17 |
And wherever there is a chance of conflict, we created aliases. |
| 18 |
|
| 19 |
This system of classification appeals to my common sense. If there are |
| 20 |
two packages with the same name in the same "general category", say, |
| 21 |
for example, perl/python modules/libraries, there will be confusion |
| 22 |
between them in the real world anyway, and one of them will *have* to |
| 23 |
change their name to prevent it. Off my head, I can think of pkgconfig |
| 24 |
crashing and burning if it got involved in such a dispute :^) |
| 25 |
|
| 26 |
> |
| 27 |
> I'm not sure what the best way is, but I don't think it's categories. |
| 28 |
> Perhaps some sort of UUID for packages? You could treat unique tags like |
| 29 |
> categories, but those could also be duplicated. |
| 30 |
|
| 31 |
I really don't think this needs such complicated solutions; especially |
| 32 |
when the "problem" is actually more of an enhancement to the category |
| 33 |
system, and the "solution" will complicate more than it will |
| 34 |
alleviate. |
| 35 |
|
| 36 |
Let's not forget that most package/dependency management systems |
| 37 |
(pkgconfig, PackageKit[?], dpkg, rpm, etc) make do with just one |
| 38 |
name-space -- staying one step ahead should be enough ;) |
| 39 |
|
| 40 |
|
| 41 |
- -- |
| 42 |
~Nirbheek Chauhan |
| 43 |
|
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 46 |
Comment: http://firegpg.tuxfamily.org |
| 47 |
|
| 48 |
iD8DBQFHrCWZb1z91vbKYbYRAq7AAJ96IukPElYbcamfct32NLbsRCZUjQCgxh1X |
| 49 |
JonN+76MwRb5D06b8ZWghjE= |
| 50 |
=TwMR |
| 51 |
-----END PGP SIGNATURE----- |
| 52 |
-- |
| 53 |
gentoo-dev@l.g.o mailing list |
Archives