Package naming conventions
Nikodemus Siivola <[email protected]>
| Newsgroups | gmane.lisp.cclan.general |
|---|---|
| Message-ID | <[email protected]> |
This is essentially return to "vn-cclan package naming conventions and repository organization" thread from May. What about: * Flat namespace. Packages are free to name themselves, but moderation is applied so that canonical names aren't frivolously grabbed. Eg. no "md5", unless it depends-on and provides a stable interface to various implementation specific packages (sb-md5, etc), *and* CCLAN is willing to make it the canonical CCLAN md5 interface. This obviously requires a process of some-sort, preferably lightweight. * Packages have category tags and a description. An CMUCL-specific XML parser might belong to categories Text, XML, Parser, CMUCL. Packages that don't have any implementation tags are automatically tagged "Portable". * Provide a tool to search by categories, etc. Cheers, -- Nikodemus
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Q0WhbSpkIAKPfsURArRSAJ46td/6xzvYfNnSxmT/xeU1mp6jkgCeKFpV Led+CgzP/cC9ESWA89DRwg8= =c6i6 -----END PGP SIGNATURE-----