cons-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cons 2.3.1 release?


From: Timothee Besset
Subject: Re: cons 2.3.1 release?
Date: Thu, 16 May 2002 10:40:22 +0200

I know, I periodically post here trying to get things moving. The CVS
version works fine, except for the build package problem I reported, and
the lack of a working parallel cons. A final release of 2.3.1 as the
stable version, and a clear statement that cons developement is abandonned
would be a good thing.

Last time I checked, scons was far behind in terms of features. I'm using
cons in a production environement, and I need some of it's advanced
features. It's not the right time to switch to scons yet.

TTimo

On Thu, 16 May 2002 10:33:14 +0200
Nadim Khemir <address@hidden> wrote:

> Timothee, 
> 
> Don't expect anything to happen. I pointed exactly the same problem months
> ago. 2.3.0 is the best way to kill cons, it's so broken that I almost gave
> up using cons, till some generous soul pointed to CVS.
> 
> There is a python implementation that supports parallel construction (search
> for SCons) it's a new product but it's not worse than 2.3.0. Hope this
> helps.
> 
> Nadim.
> 
> > -----Original Message-----
> > From: Timothee Besset [mailto:address@hidden
> > Sent: Thursday, May 16, 2002 9:24 AM
> > To: address@hidden
> > Subject: cons 2.3.1 release?
> > 
> > Last official cons release is 2.3.0, about a year ago. I know the CVS
> > version has several things fixed, cause 2.3.0 doesn't work for me and I
> > have to use CVS on some projects (for a dependencies fix, and external
> > commands I think).
> > 
> > A new release would be a good idea? Is Rajesh still maintaining cons as
> > stated on the web page?
> > 
> > My over problem is the lack of a working parallel cons (more on that
> > later).
> > 
> > TTimo
> > 
> > _______________________________________________
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/cons-discuss
> > Cons URL: http://www.dsmit.com/cons/
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]