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

Re: Build perl (ruby, pyhon, javahl) bindings with SYSTEM (installed) SVN libraries?

From: Peter Samuelson <peter_at_p12n.org>
Date: Wed, 30 Jan 2008 15:11:38 -0600

[Lev Serebryakov]
> It is possible to build any bindings with INSTALLED subversion
> libraries, without rebuilding them from source tree?

No. You might be able to hack the makefile to do this - I've never had
to find out.

> This feature, to build ONLY bindings with pre-installed subversion
> libraries and headers is VERY useful for package systems: it allows to
> easily create `main' subversion package and binding packages (vvery
> small and compact), which depends on `main' one. Now we (FreeBSD in my
> case) need to create four full-size packages with different options.
> It is ugly solution :(

What we do in Debian, and I think most free software integrators do the
same, is to have a single "source package" that, when built, produces
multiple "binary packages". So in Debian we generate, from a single
source and a single build process: 'subversion', 'subversion-tools',
'libsvn1', 'libsvn-dev', 'libsvn-doc', 'libapache2-svn', 'libsvn-perl',
'libsvn-java', and much much more.

The single source package makes sense because subversion.tigris.org
ships a single tarball. I think if you want to split up the build
process, you probably want to split it all the way up, including
multiple source tarballs.

Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-30 22:11:51 CET

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