Re: How to build the svn-client only from source tarball

Steve Greenland wrote:
> On Fri, Feb 11, 2005 at 02:59:31PM -0000, Max Bowsher wrote:
>>
>> There is no way to select a client only build, because the only thing you
>> would save would be 5-10 seconds of compilation time, which is rather
>> irrelevant in the context of the several minutes for the rest of the
>> build.
>
> It must be a pleasure to never have to work on slow machines.

Client only-ness only applies to the compilation of svnserve. That's _one_ C
file, and _one_ program link. A tiny amount of processing compared to the
rest of the compilation.

> In particular, I could significant time on some of my machines if I
> could tell it
>
> - Don't even look for BDB
> - Don't even look for Apache stuff
> - Don't even look for SWIG, or python, or perl, or java.
>
> (Yes, there are options to do that, and I use them.

Excellent, that's what they are there for.

> But they don't work reliably

If so, we would be happy to listen to bug reports and fix it.

> I think they are not always passed to the sub-configures.)

Subconfigures? The only subconfigures run are apr, apr-util, and neon.

Are you speaking of apr-util still looking for BDB? That's the only thing I
can think of.

If so, see the apr-util configure --help for appropriate flags.

> Max, I understand you don't care about this. Would you accept a patch
> that implemented a reasonable --client-only, for those of us that do?
> I think a reasonable 'client-only' definition is

> no BDB support, and

Which will happen on it's own if BDB is not found. (Via a *quick* test
querying apr-util).

> built only svn, no attempt to build the admin tools,

svnserve and svnlook could be left out, but the compilation time of those
compared to the libraries makes the extra configure machinery to
conditionalize them seem vastly overcomplicated.

> webdav stuff,

Won't be built anyway if apxs isn't found.

> language bindings, etc.

Aren't built by default anyway.

> For those of us who need to support a variety of
> architectures locally, this would be useful.

If you are supporting a variety of architectures, surely it can't be too
much trouble to write a 1-line script containing your preferred ./configure
invocation?

> If nothing else, it would
> shutup the people who can't find the --client-only configuration option.

A few emails here and there, versus a non-trivial amount of extra complexity
in the build-system.

So, I'm voting -0 on a --client-only patch.
That's not a veto - you can try mail dev@ and persuade some other committers
that it would be good idea if you like - but I personally won't be the one
approving this.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 11 21:09:27 2005