[eresi-dev] [eresi-crew] Build system

[jfv]

Hello,

Thanks for your Makefile patch, it has been included in svn
already.

As discussed online, let me answer in public:

> I'm currently trying to package ERESI for Gentoo Linux. Doing so I found
> several problems with the Makefiles, one of which breaks builds for me.
> The others are more like improvements than bugs. On the whole, most
> Makefiles should be rewritten, I think. Should I do so and send you the
> patch, or are there any plans to switch to autotools, cmake or similar
> in the near future, so that my work would be in vain?
>   

There is no plan for using autotools in the future. The truth
is that we used to be based on autotools and decided for
subtle and less subtle reasons to switch to a manual
build system.

Also, we do not plan to touch Makefiles soon (or it will be
very minor changes like adding a file to be compiled), so
feel free to modify them and provide a patch to be included
in svn.


> By the way, what is the current version of ERESI? 0.82a10 as the
> homepage states? 0.8a25 as in doc/VERSION? 0.82b2 as egrep
> 'REVM_(RELEASE|VERSION)' librevm/include/revm-io.h hints?
>   

0.82b2, as updated everywhere.

> Does the "a" and "b" stand for "alpha" and "beta"? Is 82 really the
> number 82, or more like 8.2, such that I'd have to expect a version 0.9
> to come after 0.8x?
>   
a = alpha, b = beta, 0.9 follows after 0.8


> Are you planning to tag final releases in SVN? Maybe even create tarballs?
>   

Yes, but there is a certain number of bugs in the testsuite
and its still being fixed. Documentation also has to be
improved before we announce a release.

-JFV