On 7/7/14, 17:22, Michael Tremer wrote:
Are you sure that subversion needs apr at runtime? It certainly needs the library, but I think that everything that is needed by subversion at runtime should be in the core system already.
We had a subversion package which was dropped in 2008, because the IPFire project switched to git and there was no one who wanted to maintain subversion any more.
http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=a91ca65e82da80139f0e0...
Long story, but I'm curious about why apache makes used of bundled third party sources here, is this a special case that requires to go against what's encouraged?
APR is a part of apache. Some distributions simply create a subpackage for apr as it is usually not needed at runtime, just for development.
OK, that all makes sense. So I might as well just point the subversion ./configure script to use the ones in httpd sources for the build and be done with it. I don't mind maintaining the package (and other orphan packages that I may want to use from time to time). What does this usually entail? Just following the upstream project for bug and security fixes and re-building new sources when that happens?
-- GH