Apache and APR have been split (currenly in hardmask, will be moving to unstable shortly) and configuration paths and module locations have been changed. Subversion should use the apache-module eclass to build it's apache module(s), and the variables from depend.apache eclass to get correct installation locations. Documentation on both eclasses and what has changed is at http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html I believe trapni had made some changes (looks like now removed) and wanted to help maintain subversion and it's apache modules, you may want to get with him on that.
Nah, I made a masked version that actually merged trapni's changes with the latest ebuild. Trapni's ebuild was based on an older version of the ebuild, and also removed support for apache alltogether. I created a new masked version that is actually correct.
I've revised the 1.1.3-r1 ebuild to use the new apache.depend eclass.
What I did was NOT (I repeat: "not") wrong. the apache module has been extracted onrequest (as part of our big TODO list) into dev-util/subversion and www-apache/mod_dav_svn. So, please do not add it back.
I will have the apache module in subversion. The maintenance is allready complicated enough without the apache module being somewhere else. As I'm still the maintainer of this package I will keep it in there and that is final. I don't mind for the module ebuild to be a meta package that just gets subversion, but will not support module packages that overlap. With the apr/apu stuff split out of the package things should be manageable now. The module is an integral part of the package in server mode and as such will stay in.
The new apache is unmasked, the new subversion isn't. What's up with that? # emerge -uDpv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [blocks B ] dev-libs/apr (from pkg dev-util/subversion-1.1.3) [ebuild N ] app-misc/mime-types-1.0-r1 5 kB [ebuild N ] net-www/gentoo-webroot-default-0.1 -no-htdocs 74 kB [ebuild N ] dev-libs/apr-0.9.5 -debug +ipv6 997 kB [ebuild N ] dev-libs/apr-util-0.9.5 -berkdb -gdbm -ldap 703 kB [ebuild U ] net-www/apache-2.0.52-r3 [2.0.52-r2] +apache2 -debug -doc -ldap -mpm-leader -mpm-metux -mpm-peruser -mpm-prefork -mpm-threadpool -mpm-worker -no-suexec +ssl -static-modules -threads 5,127 kB Total size of downloads: 6,908 kB
Apparently it was forgotten in the unmask. I unmasked it, so it should be in your tree in an hour.
pauldv: why don't you want mod_dav_svn out in its dedicated ebuild? maintaince complexity can't be the reason as I already sent you a mail request to voluntier my help in maintaining. however, you ignored it (instead of declining/accepting). I'd just like to know why you don't want it this way. What's so bad in splitting it.
trapni, I must confess that I lost your email and forgot that you send it. For the splitting, it will create all kinds of subtle bugs. In principle subversion and the module should be synchronized in version. There are also many subtle libtool bugs in subversion complicating things further. Also the module is an important part of subversion that has historically allways been a part of subversion.
So will this work now? Can I start using the new apache and then svn-1.1.4 w/ mod_dav_svn?
For mod_dav_svn you need to specify the apache2 useflag, but then it works. New subversion versions will only use the split out apr/apr-util ebuilds. The mod_dav_svn ebuild is obsolete
