Re: pkgsrc: libidn

["Steve O'Hara-Smith" <steve@xxxxxxxxxx>]

On Mon, 23 Mar 2009 01:17:34 +1100
Petr Janda <elekktretterr@exemail.com.au> wrote:

> Hi Hasso,
> Thanks for your reply.
> 
> On Mon, 23 Mar 2009 00:24:53 Hasso Tepper wrote:
> > And if the library contains API/ABI incompatible change?
> >
> How do other package managers handle it? I personally like the way 
> applications for Windows usually handle it by bundling the required
> libraries with the software itself(provided its done smart, and not by
> simple copying of the libs into C:\Windows, and yes there are problems
> with this approach as well but thats because of Windows itself not
> because of the approach.)

	FreeBSD's portupgrade handles it by keeping copies of the old
libraries in a directory set aside for old libraries so that new compiles
don't link against them but old compiles can find them. The downsides are
that it can be hard to tell when an old copy can be safely removed, and if
the library update is a critical one (security for example) then you really
want everything to be relinked to the new library.

-- 
Steve O'Hara-Smith                          |   Directable Mirror Arrays
C:>WIN                                      | A better way to focus the sun
The computer obeys and wins.                |    licences available see
You lose and Bill collects.                 |    http://www.sohara.org/