On Sep 13, 1:44 am, Stuart Sierra wrote:
> > Since the new, separated contrib libraries are supposed to be
> > compatible with Clojure 1.2, you could perhaps also start migrating
> > one lib at a time at your leisure. This might even enable you to
> > contribute to a migration document.
>
> Yes,
> Since the new, separated contrib libraries are supposed to be
> compatible with Clojure 1.2, you could perhaps also start migrating
> one lib at a time at your leisure. This might even enable you to
> contribute to a migration document.
>
Yes, this is what I am hoping people will do. Move to
Hi
On 12 September 2011 11:43, Jan Rychter wrote:
> On Sep 10, 9:31 pm, Sean Corfield wrote:
>> On Sat, Sep 10, 2011 at 9:46 AM, Jan Rychter wrote:
>> > If you use Clojure to build an application that you subsequently
>> > launch and maintain, it is pretty much a given that you use contrib.
>>
On Sep 10, 9:31 pm, Sean Corfield wrote:
> On Sat, Sep 10, 2011 at 9:46 AM, Jan Rychter wrote:
> > If you use Clojure to build an application that you subsequently
> > launch and maintain, it is pretty much a given that you use contrib.
> > Lots of it, in fact.
>
> I think that depends on when yo
On Sat, Sep 10, 2011 at 2:52 PM, Luc Prefontaine
wrote:
> We were in production in Jan 2009 before Clojure 1.0 came out.
> We face the issue of un-rooting ourselves from the "old" contrib stuff.
>
> After analysis, 97% of the stuff we need from the "old" contrib is now
> available in 1.3
> as sep
+1
We were in production in Jan 2009 before Clojure 1.0 came out.
We face the issue of un-rooting ourselves from the "old" contrib stuff.
After analysis, 97% of the stuff we need from the "old" contrib is now
available in 1.3
as separate libs.
The only thing we would like to keep is the trace m
On Sat, Sep 10, 2011 at 9:46 AM, Jan Rychter wrote:
> If you use Clojure to build an application that you subsequently
> launch and maintain, it is pretty much a given that you use contrib.
> Lots of it, in fact.
I think that depends on when you started building stuff with Clojure.
I get the impr
On Fri, Sep 9, 2011 at 11:04 AM, Sean Corfield wrote:
> On Fri, Sep 9, 2011 at 1:09 AM, Jan Rychter wrote:
>> Take an example -- even in the relatively simple case of
>> clojure.contrib.combinatorics: note that it is NOT listed on
>> http://dev.clojure.org/display/doc/Clojure+Contrib, and if I fo
On Sat, Sep 10, 2011 at 2:59 AM, Jan Rychter wrote:
> Thanks for the explanations. I'll summarize: clojure-contrib is being
> reorganized. There is no clear migration path for applications that
> use the monolithic 1.2 contrib. Not all of 1.2 contrib code made its
> way into new modules yet. There
> My worry is that the decoupling of "core Clojure" from contrib will
> result in contrib authors not caring too much about sorting out the
> current situation. Also, I think much of the fanfare of the 1.3
> release will be shadowed by the contrib situation. And perhaps most
> importantly, I worry
On Sat, Sep 10, 2011 at 12:46 PM, Jan Rychter wrote:
> On Sep 10, 5:20 pm, Steve Purcell wrote:
> > David Nolen writes:
> > > Waiting for contrib authors to sort out their libraries seems
> > > unrelated as to whether 1.3 should or should not be released. That's
> > > like delaying Python 3 bec
On Sep 10, 5:20 pm, Steve Purcell wrote:
> David Nolen writes:
> > Waiting for contrib authors to sort out their libraries seems
> > unrelated as to whether 1.3 should or should not be released. That's
> > like delaying Python 3 because libraries don't support it yet. It
> > still wouldn't be rel
David Nolen writes:
> Waiting for contrib authors to sort out their libraries seems
> unrelated as to whether 1.3 should or should not be released. That's
> like delaying Python 3 because libraries don't support it yet. It
> still wouldn't be released.
Except that Python 3 comes bundled with many
+1
We have production code here and would like to see 1.3 out even if the contrib
issue
resolve itself later. The first stable release of 1.3 needs to get used as
widely
as possible.
If some issues emerge in 1.3 it would be better to know it as early as possible.
There are significant blocks of
On Sat, Sep 10, 2011 at 5:59 AM, Jan Rychter wrote:
> On Sep 9, 8:04 pm, Sean Corfield wrote:
> > On Fri, Sep 9, 2011 at 1:09 AM, Jan Rychter wrote:
> [...]
> > > I think issues like that are fundamentally important if Clojure is to
> > > be adopted for production work.
> >
> > I agree - which
On Sep 9, 8:04 pm, Sean Corfield wrote:
> On Fri, Sep 9, 2011 at 1:09 AM, Jan Rychter wrote:
[...]
> > I think issues like that are fundamentally important if Clojure is to
> > be adopted for production work.
>
> I agree - which is why I'm pushing on clojure-dev for some serious
> attention to be
On Fri, Sep 9, 2011 at 1:09 AM, Jan Rychter wrote:
> Take an example -- even in the relatively simple case of
> clojure.contrib.combinatorics: note that it is NOT listed on
> http://dev.clojure.org/display/doc/Clojure+Contrib, and if I follow
> the github repos I'll end up in https://github.com/cl
I partly agree with Jan at:
> Problem is, none of those pages help with my problem
However,
> there are bugs in 1.2 contrib which only get fixed in the 1.3
> version, which I won't be able to use.
AFAIK new contrib is not only for 1.3 (for now).
In http://dev.clojure.org/display/doc/Clojure+Co
On Sep 8, 10:36 pm, Armando Blancas wrote:
> There's this page:http://dev.clojure.org/display/doc/Clojure+Contrib
>
> Here's the main page for the new repos:https://github.com/clojure
Problem is, none of those pages help with my problem: how do I go from
a list of 1.2 clojure-contrib modules to a
Hi,
I'll take care of c.c.trace. Just need to register on clojure-dev, my CA should
be in by tomorrow.
Luc P.
On Thu, 8 Sep 2011 16:49:42 -0700
Sean Corfield wrote:
> On Wed, Sep 7, 2011 at 5:44 AM, Jan Rychter
> wrote:
> > How do we mere mortals (that develop and maintain large apps)
> > mi
On Wed, Sep 7, 2011 at 5:44 AM, Jan Rychter wrote:
> How do we mere mortals (that develop and maintain large apps) migrate
> to 1.3?
It's a good question - and it's being discussed right now on the
clojure-dev list because the biggest obstacle to folks moving to
Clojure 1.3 is what to do about co
Just my 2 cents: If you are ok with a quick dirty hack you can fix contrib
libraries locally.
--
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
There's this page:
http://dev.clojure.org/display/doc/Clojure+Contrib
Here's the main page for the new repos:
https://github.com/clojure
On Sep 7, 5:44 am, Jan Rychter wrote:
> How do we mere mortals (that develop and maintain large apps) migrate
> to 1.3?
>
> I thought I'd be able to at least e
How do we mere mortals (that develop and maintain large apps) migrate
to 1.3?
I thought I'd be able to at least estimate the effort involved for our
application in about an hour today, but failed. In spite of searching,
looking through various repos, reading the wiki and in general
googling around
24 matches
Mail list logo
