[xcvb-devel] State of the project

[Faré]

Dear Alexander,

> I'd like to know whether xcvb can still be considered an active project
> and the maintainer(s) still want to approach a 1.0 release anytime soon.
>
Yes, I've started working on it again, and
I am aiming at having something more usable by the end of next summer.
Mind you it's working already, but usability is low, and
it's definitely not in shape to replace ASDF:
right now, it's Linux-mostly, SBCL, CCL or CLISP only.
And error reporting sucks.

> If so, it might be worth looking into integrating xcvb with evol[1]
> where the former depends on Make right now.
>
Well XCVB now has a Linux-only non-make backend, but
without any good story for error-handling.

> While started as a long-term
> Autotools replacement, it can already be used for dependency resolution
> and multi-threaded building and I'd happily support xcvb development,
> also in order to push evol's code base.
>
I looked at the Cliki page. Looks interesting. We should discuss.
Do you have Google Talk? I'm fahree at gmail.com. Skype? I'm fahree.

> [1] http://cliki.net/evol

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
We reject: kings, presidents and voting. We believe in:
rough consensus and running code. — David Clark for the IETF