[PATCH] kdevelop subversion part patch

Andreas Pakulat apaku at gmx.de
Mon Feb 26 15:49:47 UTC 2007

On 26.02.07 10:09:37, Kris Wong wrote:
> > We don't need to worry the run-time dependency.
> > Let's think about some actual kdevelop user who is using subversion
> too.
> > In his computer, svn command-line tools and its libraries are already
> installed.
> > We do not need to use dlopen to use subversion libraries.
> > So, If somebody tries to compile kdevelop, the extra package he should
> install
> > is libsvn-devel. For non svn user, he can just disable subversion
> part.
> This is not entirely true.  This would assume that the package for the
> user's distribution puts the headers into /usr/include and the libs into
> /usr/lib.  Also, not all users use packages.  I know the default install
> location when buildling subversion from source puts the libraries into
> multiple different paths in /usr/local (there are about 16 different
> libraries that are needed including the apr libraries).

I'm not a subversion expert, but last time I checked programs linking
against libsvn needed only apr, aprutils and neon. Of course those have
themselves dependecies too, especially neon needs libssl, libxml2,
kerberos and pkg-config. But thats exactly the reason why packaging
systems exist. I personally think we shouldn't care too much about
people not using any packaging system at all (I'm not talking binary
packages, I also mean source packages), those have the same kind of
problems with the Rest of KDE and any other non-trivial software they
want to install.


It may or may not be worthwhile, but it still has to be done.

More information about the KDevelop-devel mailing list