Veracity doesn't compile on GCC 4.4 due to enabling -Werror and making silly mistakes like comparing signed & unsigned integers. I fixed that here: http://github.com/avar/veracity/commit/ffda987d8b
It also doesn't work on 64-bit machines due to mismatched size comparisons. And I confess to finding it humorous you're submitting a patch to Veracity using Git.
Considering their bread and butter last I knew was source control, wonder if they plan to make money off support contracts, tools on top of it, or something else.
Tools, training and support. Distributed version control is making its inroads into large IT shops. It makes sense to get out in front of that and create a product where you have the market position to allay CIO's fears of an unsupported OS product like git or mercurial. "Sure, you can pay company X to support git but go with us and Veracity - we wrote the code."
Geez, do we really have to explain that HERE? At the O’Reilly OPEN SOURCE Convention?
The core of Veracity will be open source, but we plan to sell other products and
services on top of that core."
A tarball and a mailing list? Really? Aren’t you going to have some kind Web 2.0 "Veracity Overfow" thingie?
Veracity’s web presence will have more of the modern menities later. The Veracity server needs more testing before we set up a public instance of the repo.
Hmm, pretty interesting choice of language - I would have assumed that C++ was available on all platforms as well, and it has better manual memory management than C.
