On 23/03/2019 15:30, Boris Kolpackov wrote:
I would like to add support for the build2[1] build system, similar
to how it was done recently for CMake. One of the benefits will be
continuous building and testing[2] on a wide range of platforms and
compilers[3] (currently 33). I am committing to maintaining this
support going forward.
Before doing this (and provided there is support in the first place,
of course), I would really like to migrate the project from svn to
git (hopefully with the help of Apache Infra). Last time this came
up, I don't believe there were any strong opposition to such a
switch.
I would like to put these two points to a vote but before doing so
I thought I would check what the sentiment is.
I'm doing all my work in git using the git mirror anyway,, so I would be
more than happy to use git for the main repository. It's much more
efficient.
Regarding build2, are there sufficient benefits over the existing
autotools and cmake build to make it worth the cost for supporting three
build systems? Maintaining two with exact feature parity and behaviours
is already a maintenance burden. I think three is too many, and would
recommend we drop one if we are going to support a new one. And I think
that would have to be the autotools build.
Regarding the CI side, can it integrate with Apache's github repo like
we have already for Travis and AppVeyor?
Kind regards,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
