Re: category

quoth Paul Jarc:
> <[email protected]> wrote:
> > Due time, I had same problems with mysql - it is web application
> > (because I use it only in this way) or data/mysql (which I choosed

I like category names that indicate what a package is for, rather than
what it is. Editor would be a possible good exception -- I've been
using doc (i.e. for the creation of documentation) for things like
emacs, tetex, and acroread in my own separate, unregistered
/package-like directory. I also use data/mysql, because that's what
it's for. X and windowmaker both ended up in system, along with GNU
screen and the linux kernel.

> By doing this, you risk creating problems for yourself.  Those names
> could be registered in the future for different uses.  To protect
> yourself, put these packages outside /package, or somewhere in
> /package where you have authority (either via a registration or in
> host/).

There is also an additional risk -- getting a bad headache. I like the
/package categories (I may be the only person on this list who does),
but I think that one meaningful (as much as possible) category should
be selected by the author of the package (with help from Prof.
Berstein, of course).

By all means, let's add helpful categories -- their definitions can't
be precise, but they can be helpful semantic clues that make a package
name more meaningful (to humans). That's a good thing, I think.

-- 
Lang Martin
What's that attachment?   http://cross-cc.com/lang/gpg.html
Key Fingerprint: 5621 D8D9 3E2D 489A 4381  95C9 E528 D210 F960 10B3

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: http://cross-cc.com/lang/gpg.html

iQCVAwUBPW0sQuUo0hD5YBCzAQLXdQP9Hv/mwfbEKxXwZ6PT5AOb0R7vpDTRUYL8
LhyD0E0o+hQdXMC5JAYC1+QXli3v8NAORPXk6z6tfKc9LBABG4leD9U/0cN/jEY0
kU1VQaYJ4QWEO8Nz9uVSL76f25Zje7v5NDkphqENl1RsM1iJFc954px/ro27gH7W
1TUpxiQZuro=
=8N9y
-----END PGP SIGNATURE-----