Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

Hi, On Feb 10, 12:31 am, Brian Schlining wrote: > > > That's exactly what Debian does. For every Java package also provide > > > the maven xml file and the jar is discoverable from maven. The > > > installed packages on the local system acts as a local maven repo. > > > >  

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

> > That's exactly what Debian does. For every Java package also provide > > the maven xml file and the jar is discoverable from maven. The > > installed packages on the local system acts as a local maven repo. > > > > > > I see they also solved the prob

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

> That's exactly what Debian does. For every Java package also provide > the maven xml file and the jar is discoverable from maven. The > installed packages on the local system acts as a local maven repo. > >   I see they also solved the problem of not do

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

On Tue, Feb 9, 2010 at 12:27 PM, Meikel Brandmeyer wrote: > Hi, > > maybe I don't understand the problem. Why can't the system provide > some kind of local repository? The package system (deb, rpm, ports, > whatever) just installs the dependencies there. A wrapper script reads > in the dependencie

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

Hi, maybe I don't understand the problem. Why can't the system provide some kind of local repository? The package system (deb, rpm, ports, whatever) just installs the dependencies there. A wrapper script reads in the dependencies and adds them to the classpath on program start. Nothing is download

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

> > IMHO Ruby (and probably python) do this better than Clojure, though > I'm not sure if we'll ever be able to find a solution we can all agree > on. > Groovy has a very decent solution to the classpath issue for scripts. Details can be found at http://groovy.codehaus.org/Grape . It might be wort

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

On 5 February 2010 18:47, Peter Schuller wrote: >> I've been wondering about this.  The classpath issue seems like a >> major thorn in the side of the JVM, especially for Clojure and other > > It seems to be that there are two problems here. > > One problem is that there needs to be a convention f

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

>> In short, I think that the Java and Clojure way of packaging software >> make life much easier for programmers, package maintainers, and >> administrators, not harder. Making applications self-contained helps > > I have no experience with this yet, but one reason for looking into the JVM > has

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

On 07.02.2010, at 03:25, Constantine Vetoshev wrote: > I stopped using Python and Ruby and Perl partly because the packaging > situation for all those languages is a horrible mess. For example, if I agree. It's not just packaging, even providing sufficiently general installation scripts is a dif

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

On Sat, 6 Feb 2010 18:25:47 -0800 (PST) Constantine Vetoshev wrote: > On Feb 6, 1:06 pm, Peter Schuller wrote: > > But the practical issue > > remains that if I want to write some software that I want sysadmins in > > various situations to want to use effortlessly (in my case, a backup > > tool)

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

On Feb 6, 1:06 pm, Peter Schuller wrote: > But the practical issue > remains that if I want to write some software that I want sysadmins in > various situations to want to use effortlessly (in my case, a backup > tool), problems like these do get in the way of choosing Clojure. > > Maybe uberjars

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

> How about having a Clojure application 'package' set up a launcher > script to launch the app with a minimal classpath, Leiningen style, > based on some assumption regarding the whereabouts of versioned jars > on the system? (E.g. jline-0.9.94.jar rather than jline.jar, say.) Something along tho

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

How about having a Clojure application 'package' set up a launcher script to launch the app with a minimal classpath, Leiningen style, based on some assumption regarding the whereabouts of versioned jars on the system? (E.g. jline-0.9.94.jar rather than jline.jar, say.) That seems to me to be pref

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

> My extremely biased opinion:  Clojure is not a scripting language. One can spent a lot of time debating the definition of 'scripting language', but sure. The bigger issue though: > The "binary" is java.  System-wide classpaths are a bad idea. In theory I agree with you. The concept of site-loc

Re: Prepping clojure for packaging (was: Re: Clojure for system administration)

On Feb 5, 1:47 pm, Peter Schuller wrote: > One problem is that there needs to be a convention for a clojure > "binary" that works consistently across platforms. My extremely biased opinion: Clojure is not a scripting language. The "binary" is java. System-wide classpaths are a bad idea. -SS -