Re: vn-cclan package naming conventions and repository organization

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Nikodemus Siivola <[email protected]> writes:

> I think some bit of control is good. I think that packages in this respect
> can be split into two categories:
>
>  * Those for which canonical cclan versions make sense. Like md5.
>    I mean, how many alternative md5 packages do you think we need?
>
>  * Those for which multiple implementations make sense. Like XML parsers.

I tend to agree, but someone has to decide which is canonical.
Perhaps some kind of Debian-style 'Intention To Package' procedure?

> The naming schemes could be:
>
>  category-canon        (eg crypto-md5          <- canonical package)
>  category-canon-name   (eg crypto-md5-foobar   <- alternative md5 package named foobar)
>  category-name         (eg xml-foobar          <- xml tools in called foobar)

Not sure what the difference between the last two of those is.

> This is not just a disambiguation issue, IMHO. It's also a classification
> and distribution issue. If cclan abosulety wants to use a dot-hieracrhy,

I don't care what kind of punctuation we use, really.

> Before you ask, there is a reason why I used varying categories for
> packages: I don't think it's a solved problem. Should md5 be in crypto,
> security, or is it a category of it's own?

And this is very nearly my reservation about a hierarchical scheme:
the only difference is I would have said "solvable" where you say
"solved".  When it first started up, cliki had no separate category
for XML - we put XML tools in the Text category.  As we found more XML
stuff it became obvious that list of XML stuff would be useful, so we
made one.  We could do that easily because CLiki is a flat namespace,
but to do the same kind of refactoring in this hierarchical scheme
we'd have to rename packages, which is suboptimal really.


- -dan

- -- 

   http://www.cliki.net/ - Link farm for free CL-on-Unix resources 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQE+ulxgHDK5ZnWQiRMRAnazAKC8DIAD7RgCvFDIkLA18Iz1qkDiqgCfR+L3
LaNkwAKhdyZsdGCZlwF5qS8=
=bP+6
-----END PGP SIGNATURE-----


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com