Re: Checking for broken packages (as in linking)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--14dae9399c998798ef04b1020901
Content-Type: TEXT/PLAIN; CHARSET=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.BSF.2.00.1111051643442.28513@wonkity.com>

On Sat, 5 Nov 2011, C. P. Ghost wrote:

> On Sat, Nov 5, 2011 at 7:27 AM, James Colannino <james@colannino.org> wrote:
>> No, I don't mean checking for broken ports :-P 슠In fact, when I Google
>> around for the answer to my question, that's all I can find, which is why I
>> bring my question to the mailing list instead :) 슠Maybe "broken ports" or
>> "broken packages" isn't the right term (what should I be searching for
>> instead?)
>>
>> What I want to know is, are there tools that will check the ports I've
>> installed and tell me if any of my packages are linked against libraries
>> that are no longer there? 슠I'm paranoid that at some point, while I'm
>> building and installing updates, I'm going to break something.
>
> I'm using the following script (attached).

There's also pkg_libchk from sysutils/bsdadminscripts.
--14dae9399c998798ef04b1020901
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
--14dae9399c998798ef04b1020901--