Jerome Renard <jerome.ren...@gmail.com> wrote on 12/04/2011 07:23:
Hi Gaetano,
On Mon, Apr 11, 2011 at 10:06 PM, Gaetano Giunta
<giunta.gaet...@gmail.com> wrote:
Jerome Renard wrote:
Hello,
I started to create an Ant based version of the Makefile available in
website/
The problem with the Makefile is that it does not work at all on Mac Os X
and
is kind of hard to read.
Thanks for the work but I find ant kind of not working on windows (a lot of
tasks still do rely on cli tools) an extremely hard to read.
Well I tried to use ant targets as much as possible in order to avoid direct CLI
accesses. By reading this message I realize I did not do a good enough job as
a few CLI calls are still system dependant (#fail) the calls are :
- svn
- which (for which phpdoc)
- php
I will provide properties to define the path to each of them. That way
everyone can
control the path to SVN, PHP etc, etc
Note about the SVN CLI calls:
Initially I wanted to use the native Ant SVN tasks, but I failed at
grabbing them through
Ivy (the ant dependency manager used in the build file when you run
ant-install-dependencies).
So I falled back on a standard CLI call.
What about migrating to pake instead?
. based on php, should be runnable everywhere the zetac are
. cross platform
. increases interaction with the rest of the php community
You can look at
http://svn.projects.ez.no/ezextensionbuilder/branches/pake_based_rewrite/
for a bootstrapping, self-updating pakefile script (of corse, based on JC's
original ant work ;-) ). it uses the zetac for generating html docs out of
.rst and for creating zip/tgz tarballs
Well, this serves another purpose. The goal of the website's build
file is to make
people able to update and contribute to the documentation by either
providing patches
or committing changes directly. But in order to test their changes
they need to rebuild
the website. For the moment using the Makefile works fine for anyone
who uses Linux.
For other users that's not possible and that possibly blocks people
who would be interested
in improving the documentation.
Using Pake (or any other PHP based build system) is to make people
able to modify and
(why not) extend the build system. I would say it is a lower priority
as if you can not build
the documentation, you will not contribute to it and you will
obviously find no point in updating
or extending the build system.
Not to split hair or make this thread overly long, but I fail to see your point
here.
Using a build system's goal is never for "having fun hacking it" in the first place, but to produce a build, be it docs, the website, binaries, or a tarball of
sources.
Making the build script easier to hack and more portable is just a way to make sure that the 1st goal is reached, by giving more people a chance to understand
it, test it on their own environment and submit patches / improvements.
bye
Gaetano
