From owner-freebsd-ports@FreeBSD.ORG  Tue Nov 26 18:15:33 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7528F260
 for <freebsd-ports@freebsd.org>; Tue, 26 Nov 2013 18:15:33 +0000 (UTC)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2E3E82224
 for <freebsd-ports@freebsd.org>; Tue, 26 Nov 2013 18:15:33 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.7/8.14.7) with ESMTP id rAQIFW6n056953;
 Tue, 26 Nov 2013 11:15:32 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rAQIFWx7056950;
 Tue, 26 Nov 2013 11:15:32 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Date: Tue, 26 Nov 2013 11:15:32 -0700 (MST)
From: Warren Block <wblock@wonkity.com>
To: Kevin Oberman <rkoberman@gmail.com>
Subject: pkg_libchk (was Re: gvfs on FreeBSD 10 fails to build)
In-Reply-To: <CAN6yY1siA=s5AvCt8xAjzMu6+2DzT+agNQi+pFaqxtQZ-wwYKA@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1311261113010.54550@wonkity.com>
References: <529453E6.3080200@gmail.com> <5294684E.1050105@passap.ru>
 <52946CE3.5010802@gmail.com> <5294757E.3010309@passap.ru>
 <CAN6yY1siA=s5AvCt8xAjzMu6+2DzT+agNQi+pFaqxtQZ-wwYKA@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Tue, 26 Nov 2013 11:15:32 -0700 (MST)
Cc: Johan Hendriks <joh.hendriks@gmail.com>, Boris Samorodov <bsam@passap.ru>,
 FreeBSD <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2013 18:15:33 -0000

On Tue, 26 Nov 2013, Kevin Oberman wrote:

> Possibly hijacking the thread, but isn't it time that pkg_libchk was made a
> part of the base system? It comes up over and over as a tool to simplify
> dealing with dealing with shareable library version bumps and even more
> important for dealing with the problem seen here. It's a fairly simple,
> well written, maintainable shell script, so will run with no dependencies.
> I can't think of any reason not to include it in the base system.
>
> Checking for issues with shareable libraries is an obvious requirement for
> maintaining a system and doing so without a tool like pkg_libchk is
> unnecessarily tedious and painful.

Maybe integrating it with pkg rather than the base system.  At least for 
me, it's not a problem with the base.