On Feb 25, 2009, at 6:14 PM, Laurent PETIT wrote:
I've already answered to the external stuff in another message (and sorry for having been so crude, but I really think it's not a so good idea. In that particular case : clojure does not depend on clojure contrib. So clojure svn must not depend on clojure-contrib svn).
Thanks for the discussion. I understand your objections and in the face of them I estimate the probability of any of these changes being adopted to be 0. The status quo, where there is a complete separation of clojure and clojure-contrib, is in some ways (perhaps many ways) simpler than using a feature of svn to combine them. Simplicity is a high value and I'm sure it will win the day. I have no objection to that.
For my own education, I just re-read the documentation at red-bean and there is nothing mentioned there in the externals section about dependencies. What they talk about is keeping code that's logically part of one thing in separate repositories (or separate locations within one repository). That's exactly the case with clojure and clojure-contrib.
It seems to me that the dependency scenario you describe is one use of externals, but not necessarily the only one.
clojure-contrib is logically part of Clojure:- The contrib namespaces live in a namespace under the "clojure." umbrella.
- The licensing and contribution requirements are exactly the same. - Code can (and has) flowed from clojure-contrib into clojure.My understanding is that the primary reason contrib code was put in a separate svn repository is that doing so provides a clean way to have a few more committers for clojure-contrib than the one committer for clojure. Another benefit of having them separate (which would be preserved in a clojure/contrib setup) is that it's clear which parts of Clojure have Rich's full support and which parts don't.
This external mechanism in svn looks like it would allow all the benefits of keeping them separate while avoiding some of the minor annoyances that come with them being separate--like knowing where clojure is installed doesn't give you any info about where clojure- contrib is installed.
Concerning the https vs http problem, I haven't checked svn redbook recently (and I don't know exactly which svn version googlecode is running), but at some time in the past, it was tricky (if not impossible) to do edits and commits in an external.
Thanks for that info. --Steve
smime.p7s
Description: S/MIME cryptographic signature