Hello! This is the ebuild for the new version of subversion 0.31.0 And this ebuild depend on dev-libs/apr-0.9.4 * compiled svnadmin statically as svnadmin-static for future incompatible changes like 0.28.0 * fixed permission of tools directories. 751 -> 755 * chown -Rf apache.apache -> chown -Rf apache:apache Thank you.
Created attachment 19042 [details] subversion-0.31.0.ebuild
If you feel you must submit a corrected ebuild next time. Could you then please take the latest ebuild from cvs as a starting point. This ebuild is not really useful as such. About apr, now that there is actually a current release I will look into using a virtual/apr dependency instead of using the internal apr. I did submit a 0.31.0 ebuild though, so I'm closing this.
OK, I understand, But please let me explain why I posted like this. The difference between my ebuild and your ebuild. * IUSE "ssl" == --with-ssl This configure option was used by neon's configure script, so this is not needed. * DEPEND ~sys-devel/m4-1.4 I can't understand this syntax, this syntax was undocumented. >=sys-apps/diffutils-2.7.7 >=sys-devel/libtool-1.4.1-r1 >=sys-devel/bison-1.28-r3 These things are not needed (and also m4), because these are already installed, if you ran "emerge system" before. * src_unpack() subversion-db4.patch This patch is not needed. The current subversion's configure script can detect the db4 on Gentoo, like this: from ./configure checking for Berkeley DB in the standard places (as db4)... no checking for Berkeley DB in the standard places (as db)... yes end So following lines are not needed. export WANT_AUTOCONF_2_5=1 elibtoolize autoconf (cd apr; autoconf) (cd apr-util; autoconf) * src_compile() use berkdb && myconf="${myconf} --with-berkeley-db" use python && myconf="${myconf} --with-python=/usr/bin/python --with-swig" Perhaps, these are not needed, because this is default. --disable-mod-activation This option is needed if you want to build apache modules, but this is harmless even if specify. emake external-all && emake local-all If you do not trust "emake", you can use "make". But "emake" worked correctly, you can verify this by "make test". And static linked svnadmin was not needed? In the Debian's package that still provided static linked svnadmin as svnadmin-static. If you want to provide static linked svnadmin, you must add following line before make, if you do not do that you can not make svnadmin statically. I do not know why, but link of pthread library failed. libtoolize --copy --force --automake cp /usr/share/aclocal/libtool.m4 ac-helpers * src_install() Please install "tools" directory. This directory contains sample of hook-script, and other sample. And this directory's permission is wrong (751), so please correct the permission to 755. * pkg_config() "chown -Rf apache.apache" should be "chown -Rf apache:apache" ~~~ ~~~ From this thread: http://article.gmane.org/gmane.linux.gentoo.devel/12847 If you already know this, sorry. Sory for my English. Thank you.
I'll check about ssl, and the dependencies. However, the db4-patch is necessary. elibtoolize is too as it fixes the link order and as such makes sure that at installation time the libraries get linked against their new peers and not against the old libraries. That can cause all sorts of mayhem. For --with-db etc. even if it is the default we are safer if we specify them anyway. That will protect us against changes away from the default, and in many cases forces the configure script to fail if they are not available, while if they are not specified the script will ignore the fact they are missing. The static svnadmin provided is the old one. There is not much point in providing a new static svnadmin. The only alternative would be to actually build the static svnadmin from the 0.27 sources instead of downloading one I compiled. It is not that you will use it more than once. The make external-all && make internal-all is used to make sure that paralel makes work correctly in all cases. Further I'll look about what I will do with the tools directory.
