when i emerging subversion-0.10_pre1, the following error has occured. -------- # emerge subversion (snip) configure: checking neon library checking neon library version... 0.21.3 You have neon version 0.21.3, but Subversion needs neon 0.19.2. Please either install neon 0.19.2 on this system or get neon 0.19.2 from: http://www.webdav.org/neon/neon-0.19.2.tar.gz unpack the archive using tar/gunzip and rename the resulting directory from ./neon-0.19.2/ to ./neon/ configure: error: no suitable neon found !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile_svn, Line 16, Exitcode 1 !!! ./configure of subversion failed !!! emerge aborting on /usr/portage/dev-util/subversion/subversion-0.10_pre1.ebuild . -------- in subversion-0.10_pre1.ebuild, it depends on '>=net-misc/neon-0.19.2' , but should it be '=net-misc/neon-0.19.2' ? after i downgraded neon to 0.19.2-r1, emeging subversion was succeeded.
I've done an emerge rsync, and the only version of neon listed is 0.21.3. Unless there is some way to retrieve old versions of packages that I don't know about, subversion can't be installed using just emerge.
That is correct. Subversion is very particular about which versions of neon it will work with. According to the subversion development team, HEAD of Subversion will only work with HEAD of their external libs. Thus, when they do a release of subversion, it can only be expected to work with the most recent releases of their deps at the time of release. This will of course have to change when Subversion ever reaches a stable state. Because of this assumption, packaging a subversion release is a huge undertaking which none of the current developers seem to bother much about. Geert Bevin kept up with Subversion until he left the Gentoo project earlier this year. I won't touch this with a ten-foot pole; it's a huge maintenance nightmare. Say, if somebody upgrades neon because a newer version is required by, say apache, and then that somebody deletes the older versions of the neon (as they appear to be deprecated and cannot coexist with the newer version of neon anyway), Subversion will break. Or, if somebody merges Subversion which depends on neon-0.19.2, then they emerge apache with WebDAV enabled (which requires neon-0.21.x), Portage will not flag this as an error, and subversion won't work. The list goes on and on. If somebody else wants to take it on, be my guest.
*** Bug 6597 has been marked as a duplicate of this bug. ***
I've just had a look and old versions of Neon seem to be available. Recent versions are on the main homepage (http://www.webdav.org/neon/) and older versions are on the archive page (http://www.webdav.org/neon/history.html).
In fact, the Subversion source tarballs (wll include the source for the appropriate versions of apr, apr-util and neon. There is no need to download the files separately. For example, http://subversion.tigris.org/files/documents/15/841/subversion-r3200.tar.gz.
Couldn't subversion, like cadaver, be built statically linked to avoid this problem? What would actually be most useful would be to have a subversion client ebuild; with it it would be possible bootstrap a CVS version of subversion. A server installation script is just too much trouble given the unstable nature of the project.
Subversion is self-hosting (ie. stored using itself), so it would not be possible to build it from CVS. Also, the latest version from the repository is probably less stable than the latest drop.
Pardon, I meant SVN, not CVS :).
Created attachment 6598 [details] Subversion 0.16 ebuild Here's the ebuild I've been using for subversion 0.16. I'm not much of a C/C++ programmer, but it worked for me.
Is that attachment an ebuild file? I think it might have been corrupted, it's not a text file when I download it. Or maybe I'm doing something wrong.
James, I see only a binary for your ebuild attachment: could you upload your text ebuild again perhaps? This whole subversion situation *does* seem to be a mess....
Created attachment 6846 [details] ebuild text only Here's just the ebuild. The previous attachment is a tar.gz of the ebuild and /etc/init.d/subversion script, but I somehow lost the extension.
I just made a new ebuild available for subversion 0.16.1. The ebuild I made does not rely on bootstrapping subversion, as most of use really don't need that. It's a lot simpler, and likely is more reliable than the old style ebuilds for subversion. See bug #14040
Bouncing back to bug-wranglers due to time constraints.
See new ebuilds at http://cvs.gentoo.org/~alain/
