Hi,

yekcim brought this topic recently. This involves a script at least
compiling and ideally building a package out of svn. Bonus
points for whoever can also generate a webpage storing a history of the 
compilations.

To do that, I can see the following method:
1) Trigger a test whether to recompile or not, for instance a cron job
or  a svn post-commit script (I know projects that for instance use them
to reject files with tabs and so).
2) Run autogen.sh
3) Run configure
4) Launch make
5) Run a script for the packaging (one exists for windows, I see none
for Debian?)

While technically feasible, this has several difficult problems:
- there is a potential mixture of ftp, web page creation and the like
that is troublesome
- the machine would have to dedicate a good amount of time to this process
- some updates may compile but resulting in a segfaulting binary or not 
runnable one (for lack of dependencies)

I'm personally not sure it is feasible unless someone can maintain a
computer on every day and night.

So...
I consider the benefits (svn verification, automatic builds for at
least one environment) not worth the effort, but yekcim thought otherwise.

Thoughts?
Volunteers !? :-)

Best regards,
Kurosu


_______________________________________________
Wormux-dev mailing list
Wormux-dev@gna.org
https://mail.gna.org/listinfo/wormux-dev

Répondre à