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).

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.

-- 
Laurent

2009/2/26 Stephen C. Gilardi <squee...@mac.com>

>
> On Feb 25, 2009, at 5:51 PM, Achim Passen wrote:
>
>  Another way to do this is to add contrib as an svn external:
>> http://svnbook.red-bean.com/en/1.0/ch07s03.html
>> Set up like this, an "svn update" in the root directory would update both
>> projects.
>>
>
> Very cool. I saw this kind of thing in action for the first time yesterday
> when checking out Clozure Common Lisp via svn. I had no idea how they did
> that.
>
> I just tried it with clojure and clojure-contrib and it worked very
> smoothly. One potential glitch is that the external reference for contrib
> would presumably be:
>
>        contrib http://clojure-contrib.googlecode.com/svn/trunk/
>
> However, for a member of clojure-contrib, the correct entry would be:
>
>        contrib https://clojure-contrib.googlecode.com/svn/trunk/
>
> (https vs. http)
>
> Have the svn folks come up with a neat solution for that case or would a
> clojure-contrib member simply propedit his local clojure svn checkout to
> give the correct URL for him?
>
> Thanks for the pointer to the info about external!
>
> --Steve
>
>

--~--~---------~--~----~------------~-------~--~----~
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 
clojure+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to