Hi Meikel,

On Thu, Dec 18, 2008 at 11:18 PM, Meikel Brandmeyer <m...@kotka.de> wrote:
> On 19 Dez., 02:10, bc <billc...@gmail.com> wrote:
>> For clojure-contrib, it would make sense to create a matching tarball
>> whenever a Clojure release occurs. For the other 3, it would be
>> necessary for someone to test and save off a copy of the libraries
>> somewhere (that by itself  would make getting started with Clojure a
>> much easier task).
>>
>> I'm not sure what the best way to manage this (the "where" and "who")
>> would be.
>
> The "who" is probably the maintainer/developer of the
> third-party library.

Although this might seem logical, if fact it is probably not the best
solution because:
1. There are multiple inter-related projects (slime, clojure-mode,
swank-clojure) that would all need to be "snapshot-ed" simultaneously.
2. It assumes the developer(s) of the projects are interested in doing
this (SLIME developers support many lisp implementations).
3. The snapshot of all 3 inter-related projects (slime, clojure-mode,
swank-clojure) should occur after it has been confirmed that they all
currently work together with the latest clojure release.

> The "where" is probably the place
> for the "who" hosts his project.

Both swank-clojure and clojure-mode are hosted on git-hub. Although it
is possible to download a tar/zip file of the current set of files in
a git-hub repository, I didn't see any functionality to store other
"historical" snapshots.

SLIME (as mentioned above) is not clojure-specific. Historically, the
SLIME developers have not been keen to create snapshots.

>> One option would be to store files in the Clojure Google
>> Groups file area (although this could be a bit problematic since the
>> Google Groups file area isn't very "flexible" and everything is
>> jumbled in there together). Another option is to maintain the 3rd
>> party tarballs as separate "Featured" downloads in the clojure-contrib
>> Google Code Downloads area. I think the latter might make more sense
>> as it would keep "release-related" tarballs all in the clojure-contrib
>> project without actually "polluting" the clojure-contrib source
>> repository with foreign libraries. It would also provide "ownership"
>> of the process (assuming the clojure-contrib members are willing to
>> take this on).
>
> I don't think, that the Google Group is a suitable
> place for such files. Concerning the contrib download
> area: who decides, which projects are allowed to go
> there? Who plays the postman who puts up the files?
> (The upstream author is probably not allowed to...)

I agree, I just suggested it because it is an option. I think Google
Code is much better suited for this.

> A centralised approach would be feasible if there was
> some CCAN, where every author can upload his files
> himself.
>
> I would propose, that the files are hosted where ever
> they are hosted now with suitable labels with which
> Clojure version they work. This works out of the box
> with the least amount of trouble.

For the reasons I listed above, I don't think it's practical to do
this for slime, clojure-mode, and swank-clojure.

- Bill

--~--~---------~--~----~------------~-------~--~----~
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