Request for comments: revamped `devel/subversion' with true bindings sub-ports (not mere `set option and build everything' like now)

[Lev Serebryakov]

Hello, Ade.
You wrote 5 февраля 2008 г., 1:59:48:


> However (there's always a however :) - would it be possible to further
> extend this to subversion-client and subversion-server (the latter  
> having all the web stuff, and the former just having the basic clients).
  There is one problem: they (client and mod_dav_svn) use SAME
subversion libraies  both. Split into lib/cli/srv? Ok. Other problem
raises here: libapr. Server binaries -- mod_dav_svn -- should use
COMMON libraries with apache's libapr, so subversion libraries MUST be
linked with libapr from apache2/apache22 port/package (not with libapr
from `devel/apr'). So, CLIENT will depends on APACHE in such case (via
libraries). No profit at all :(((

> As things stand right now, when rolling out localized package sets for
> large numbers of machines, you have to go through all kinds of hoops  
> in order to not have apache (or whatever) on every machine that needs
> subversion.
  You can not have simple three packages "subversion-core",
"subversion-client" and "subversion-dav-server" where ONLY
"subversion-dav-server" depends on apache. "subversion-core" must
depends on "apache" too, if you want to have "subversion-dav-server"...

("subversion-svn-server" is one small binary, about 65Kb, without any
additional dependenies, and can be packaged with
client without problems, IMHO).

-- 
// Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>