[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.2.0-rc1 tarballs up for testing/signing

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-04-07 01:15:54 CEST

John Lenz wrote:
> On 04/06/05 17:28:20, Max Bowsher wrote:
>> John Lenz wrote:
>>> I noticed that SWIG is still required to build the tarball. In my
>>> opinion, removing the requirement that SWIG be installed to build the
>>> subversion tarball should be something that makes it into 1.2. No code
>>> changes need to take place to support this, it is only Makefile changes
>>> and build script changes so it shouldn't be a problem of testing. I
>>> attempted to hack the build system to support this, but the way
>>> build-outputs.mk is built with those python scripts is so complicated I
>>> couldn't figure out how to do it.
>
>> As you have observed, this requires an extremely nontrivial bit of
>> buildsystem work.
>>
>> 1.2 is feature frozen, so it will not be happening in 1.2.
>>
>
> One solution would be to just copy the files into the tarball inside
> dist.sh. Then there aren't any build changes that need to take place:
> just do something like
>
> cp subversion/bindings/swig/python/core.c
> $DISTPATH/subversion/bindings/swig/python
> cp ...
>
> Perhaps list the files to be copied inside a file, and inside dist.sh read
> that list and copy those files into the DISTPATH.
>
> As long as the .c files get included in the tarball, the current makefiles
> should work fine.

No. configure will still look for a swig installed on the system, and
decline to set things up for the bindings if not found.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 7 02:24:49 2005

This is an archived mail posted to the Subversion Dev mailing list.