> Sounds sensible in principle, though I think the issue for n00bs is > that configuring *anything* is a barrier because even the slightest > mistake in interpreting the documentation or configuring your > environment is pretty painful.
OK, see my response to Rick. I think we're getting stuck on a stereotype of what a n00b is, and it's hurting the discussion. I'm not suggestion (and I don't think anyone else is) that CLOJURE_HOME have anything to do with the existing setup processes. *Complete* n00bs, and by that I mean people who generally don't have much of a clue about anything, won't know or see or wish for a CLOJURE_HOME. A CLOJURE_HOME convention would help everyone else, those who use clojure-related script/projects, etc. Newcomers (perhaps that's a better word) to Clojure, who come from a general UNIX background, would expect something like CLOJURE_HOME to exist, because it's useful convention employed frequently. If it were a convention in Clojure, n00bs an non-n00bs alike would benefit from it, while those who don't need it won't be affected in any way. - Greg On Jun 30, 2010, at 5:46 PM, Mike Anderson wrote: > On Jun 30, 6:45 pm, Greg <g...@kinostudios.com> wrote: >> It seems like a lot of n00b (and non-n00b) related problems have to do with >> the location of clojure.jar and clojure-contrib.jar. People generally don't >> like having to keep track of all the clojure.jars, and it would be nice if >> it was easy to switch versions for scripts like clj and such. >> >> May I propose as a possible remedy CLOJURE_HOME. CLOJURE_HOME is the >> absolute path of a directory containing clojure.jar and possibly >> clojure-contrib.jar. Scripts should check if it's defined and use it instead >> of hard-coded paths, as an example, here's my clj script (in newLISP): > > Sounds sensible in principle, though I think the issue for n00bs is > that configuring *anything* is a barrier because even the slightest > mistake in interpreting the documentation or configuring your > environment is pretty painful. > > For n00bs, if it is much more complicated than unzipping a Clojure > distribution or navigating to the right Eclipse update site then > you're already going to lose a lot of people. > > For those of us n00bs who primarily use IDEs like myself, I'd vote for > just improving the integration with the IDE's automatic management of > classpaths / build paths etc. To give it credit, Counterclockwise does > a decent job to get people started quickly in terms of adding the > Clojure jars automatically to an Eclipse project. > > -- > 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 -- 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
