[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: The *.so files

From: Oden Eriksson <oden.eriksson_at_kvikkjokk.net>
Date: 2002-11-06 21:43:41 CET

onsdagen den 6 november 2002 21.09 skrev Eric Gillespie:
> Oden Eriksson <oden.eriksson@kvikkjokk.net> writes:
> > The common practise in Mandrake Linux is to package the "*.so"
> > files in a devel subpackage.
> >
> > Now, this doesn't seem to work with subpackage since for
> > example the client won't work without these "*.so" files.
> Kinda. The svn program should only require the *actual* shared
> objects, i.e. libsvn_ra_local-1.so.0.0. The .so files are only
> symbolic links to those files. What RH and Debian do (and thus
> Mandrake, i imagine) is put the actual shared objects (and the
> .soname symlink, i.e. libsvn_ra_local-1.so.0.0 and
> libsvn_ra_local-1.so.0) in one package and the plain .so symlink
> in the dev package. I think that's what you want to do.

Yes that seems a common practise in Mandrake.

I'm a contributer to Mandrake and I cannot change the appearance of thousands
of packages so that there are no devel sub packages. Also as I'm no coder I
can't say what's wrong in the subpackage code, other softwares don't seem to
have this problem. I suggest the subpackage developers look into this.

Regards // Oden Eriksson, Deserve-IT Networks
Check the "Modules For Apache2" status page at: 
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 6 21:42:42 2002

This is an archived mail posted to the Subversion Dev mailing list.