Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 May 2007 10:37:37 -0500
From:      "Scot Hetzel" <swhetzel@gmail.com>
To:        "Robert Huff" <roberthuff@rcn.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Specs for saving old shared libs
Message-ID:  <790a9fff0705180837h7dad477ewf35cfe2037d4ff92@mail.gmail.com>
In-Reply-To: <17997.50475.233127.735076@jerusalem.litteratus.org>
References:  <20070507184231.GA50639@xor.obsecurity.org> <1179437517.8912.5.camel@ikaros.oook.cz> <20070518075058.GB1164@turion.vk2pj.dyndns.org> <200705181409.15561.mail@maxlor.com> <17997.40528.630013.491475@jerusalem.litteratus.org> <20070518154727.019d3c31@gumby.homeunix.com.> <17997.50475.233127.735076@jerusalem.litteratus.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 5/18/07, Robert Huff <roberthuff@rcn.com> wrote:
>        <do not try this at home>
>        When in need of emergency disk space, my first trick is to
> flush /usr/ports/distfiles and /usr/obj.
>        If that's not enough, I empty /usr/local/lib/compat/pkg.  About
> one time in twenty I discover something important was depending on a
> deleted lib.  _So far_ , every time I have been able to fix this by
> sym-linking lib<foo>,N to lib<foo>.N+1.
>        </do not try this at home>
>
You don't need to use the sym-link hack, instead create an
/etc/libmap.conf file that contains:

lib<foo>.N lib<foo>.N+1

For the applications that are missing lib<foo>.N.

Scot
-- 
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0705180837h7dad477ewf35cfe2037d4ff92>