I like the name Clojure Archive.

On another note, I always wondered why xml was such a requirement for
Java dependency management.  Couldn't we design some sort of url
schema, that you could just pass to a package importer in the
program.  First time you run, it could fetch the packages or
automatically check for upgrades etc.  This could be managed in an
external file if that seems safer.  Just a simple manager that could
wget the jars (which is all essentially that package managers like
ruby gems do).

On a slightly unrelated note, how might we index packages for
exploration?  I think that packages should be indexed both by
descriptions provided by the author and by comments within the code
itself, in the docstrings of the fn's.  Eventually, maybe we could
cherry pick namespaces and even pull specific functions!

Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to