James, Just go for it. You've certainly proved you can design a library. Deliver something that works for you, and tell us if you think it's ready. If it's better than other stuff (which I suspect it will be), the community will start using it. If not, back to the drawing board.
Sean On Aug 4, 9:03 am, James Reeves <weavejes...@googlemail.com> wrote: > On Aug 4, 12:51 pm, Krešimir Šojat <kso...@gmail.com> wrote: > > > In your project you would create standard ivy.xml and ivysettings.xml > > files as described on Ivy site. Download Ivy (and Ant jars if you will > > create or use Packagers). After that you can retrieve your > > dependencies from command line > > As Piyush mentions, Rubygems is a little more straightforward to use > than that. I'd like a package manager where it was not necessary to > create a project or write any XML files before use. > > It might be possible to adapt Ivy into a package manager like this; > one that isn't tied to resolving dependencies for one particular > project. However, I'm not sure that would be any easier than writing > one from scratch. Additionally, there are a couple of benefits to > starting from a clean base: certain elements of Ivy's design could be > improved, and new features could be more easily added. > > - James --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
