On 4/6/06, Philip Martin <philip@codematters.co.uk> wrote:
> "Justin Erenkrantz" <justin@erenkrantz.com> writes:
>
> > On 4/5/06, Philip Martin <philip@codematters.co.uk> wrote:
> >> I don't recall any discussion about the ABI change implied by
> >> releasing Subversion with support for APR 1.2. Was there any
> >> discussion, did we make a conscious decision to break the ABI without
> >> changing the soname? If we simply didn't consider it then I think it
> >> was a mistake and we should fix it.
> >
> > http://svn.haxx.se/dev/archive-2004-07/0030.shtml
>
> That's some time before Apache 2.2 was released. Effectively the
> discussion happened at a completely separate time to the release of an
> Apache that triggered the ABI change. Perhaps I should have paid more
> attention, but this was an inadvertant ABI change as far as I'm
> concerned. I still think it was a mistake, and I think we should fix
> it, just like any other inadvertant bug.
The issue has nothing to do with Apache HTTP Server 2.2 - Debian's
problem is only about APR 1.0+. Hence, this topic inevitably arose
when APR 1.0 was released back in 2004. I definitely don't view it as
an inadvertant bug.
> If you are totally opposed to changing the current default SONAME, how
> about a configure option to do it?
Remember that a simple soname change isn't enough. It must embed
every library dependency Subversion imports in order to be accurate.
You'll have to come up with an encoding scheme to describe all of the
library versions in that one string. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 7 02:23:09 2006