Greg Stein wrote:
> On Thu, Oct 24, 2002 at 11:53:27AM -0500, B. W. Fitzpatrick wrote:
>
>>Nuutti Kotivuori <naked@iki.fi> writes:
>>...
>>
>>>Um. Is there a reason we cannot run gen-make.py when ./configure is
>>>run - to generate the Makefile.in before Makefile is generated from
>>>that?
>>
>>Well, we'd have to account for people who download the bootstrap
>>tarball and don't have python installed--I don't want to make python a
>>requirement just to bootstrap.
>
>
> That is exactly why it is run at autogen time. We state that packagers [who
> use/run autogen] must have Python. End-users [who run configure] do not
> require Python.
>
> I would suggest we avoid requiring Python during the configure process.
I'm only a lurker and someone who is trying to learn and evaluate svn, but as
a newbie, I think the build process is overly complicated. I would *strongly*
urge moving the autogen.sh step into the top of configure, to make a more
"normal" build process. Even when there are RPMs and tarballs of stable
releases, some will still want to get the source and build it (e.g. to get
some patch that very important to them).
And if you don't want put a dependency on Python, write the program in Perl or
"sh". I think almost everyone has Perl on their system, and if not, "sh" will
definitely be there. (I haven't looked at the program to know if "sh" can do
what you need, so that may be a bad suggestion, but Perl can do anything. :-)
HTH,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 25 21:15:24 2002