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

Buildling parts independantly

From: Julio Merino <jmmv_at_hispabsd.org>
Date: 2002-09-02 12:15:15 CEST


I'm creating some subversion packages for NetBSD. The thing is that I want
to make three packages: subversion-lib, subversion-client and subversion-server.
It should be possible for the three packages to be installed at the same time,
so none can override files provided by the other. The idea is that:
subversion-lib: provide all the subversion libraries, lib* and the documentation.
subversion-client: depend on subversion-lib and install the client program only.
subversion-server: depend on subversion-lib (also on -client??) and install the
                   apache module and the administrative tools.

I've been looking at the build.conf file, but I can't figure out how to do this
division. It is not easy, I think :(

It would be interesting that you add some configure options, so that the user
could define what to build each time. For example:
./configure --build-libs=yes --build-server=no
or something like this. If you won't do it... how could I get something similar
for the packages?

The idea I have is to provide three different build.conf files, and override
the one included in the subversion package so that it builds what I want. But
this won't be easy to maintain on subversion updates.

Can anybody give me an idea about how to do this?

Thanks a lot!
PS: Reply directly to my mail, jmmv@hispabsd.org, as I'm not subscribed to this

HispaBSD admin - http://www.HispaBSD.org
For the developer - http://buildtool.sourceforge.net
Julio Merino <jmmv@hispabsd.org>
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 2 21:42:01 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.