Hi Ralph, In some sense you can think of a cached stable install of some set of developer tools as a performance optimization. In this case, the performance being optimized is the developer's performance installing a tool set.
Like any performance optimization, it should not be made prematurely. Maybe the cost of managing the stable install outweighs the time saved over developers just grabbing the various bits. Your bad experience certainly suggests that it is time for a prepackaged slime+clojure, --but-- > Remember the context: "Getting Started." The context is NOT bleeding > edge developers who want the very latest build of everything. If you > want the very latest slime, etc., you should be on your own. If you are using Clojure you are somewhere in the neighborhood of the bleeding edge. It isn't 1.0 yet. I would love to see somebody step forward in the next few weeks and announce a cached install that works. Then I could point to it in the book before we go to print. :-) Cheers, Stuart --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
