Re: [cclan-list] vn-cclan package naming conventions and repository organization

[Daniel B. <da...@te...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Nikodemus Siivola <tsi...@cc...> writes:

> Much better then org.domain style. Looks good.
>
> I frankly have never understood what the big deal is with the multipart
> names. I can see the point in perl-style xml::parser::fastparse thing,
> since that is both reasonable and descriptive, but it drives me crazy to
> try to live with org.foobar.yadda.cl-dingdong. If definitely doesn't make
> it easier to see what the package is about.

It's not supposed to, though.  It's supposed to disambiguate packages
=2D From different people who may want to use similar names (probably
because they weren't aware of the other package already using
whatever name)

If we lose this, we have to hope that people get smarter about
choosing their package names to avoid conflicts in the first place,
or we have to get stricter about what does or doesn't go into cclan.
Who gets the "md5" package?


=2D -dan

=2D --=20

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

iD8DBQE+ulHwHDK5ZnWQiRMRAp5YAJ9Y0ujBo0wpKO+I7hqydRE2N0vl5gCdGQtX
zJX7uS2O706y/AvuILoPd8o=3D
=3Doop5
=2D----END PGP SIGNATURE-----