Re: cons development

[Dmitry Sagalovskiy]

Thanks for the info in this and the previous emails. It's hard to say how
much my company would be willing to pay for support, since the idea was
more to help "sponsor" the project to make it easier for the development
community to advance it, and not to hire a programmer to fix little things
for  us.

Well, let's see if anyone else responds with interest in advancement of
cons. Meanwhile, I'll take a look at Python, SCons, and Inline::Python.
I'd say -j is pretty big, but good derived-file caching is even bigger. If
caching in fact appears soon, and SCons keeps moving ahead at a good
speed, well, maybe it's more worth helping out SCons and switching to
that. Perl is sure convenient, but, well, it doesn't matter too much.

dmitry


On Mon, 6 Jan 2003, Steven Knight wrote:

> > In fact, my company is so interested in having active support, that we'd
> > be willing to pay for it, except that no one here has any idea how it can
> > be made to work, with free software like this.
>
> Do you have any idea what your company would be willing to pay for
> support?  Are there other people out there whose companies would be
> willing to pay for support?  If so, there might be a good opportunity
> for someone to start a niche business (as a Cons-ultant, of course...
> :-)
>
> > If cons is not being actively worked on because SCons is about to become
> > strictly better anyway, then maybe it's fine to abandon it (although I
> > know Perl already and don't feel like learning Python just to re-do our
> > build system). But if people are going to keep on using cons, then it
> > would be a shame to let a good thing just get left behind and forgotten.
> >
> > Any thoughts?
>
> SCons will probably overtake Cons in terms of base functionality pretty
> soon.  Repository support was added in 0.09.  The last big feature still
> in Cons that SCons doesn't yet have is derived-file Caching, but that
> should be coming in 0.11, probably a month away.
>
> FWIW, unless you're doing a lot of sophisticated Perl manipulation in
> your Conscripts that would have to be translated, the Python learning
> curve when transitioning to SCons is very shallow.
>
>         --SK
>