Date: Tue, 26 Nov 2013 11:15:32 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: Johan Hendriks <joh.hendriks@gmail.com>, Boris Samorodov <bsam@passap.ru>, FreeBSD <freebsd-ports@freebsd.org> Subject: pkg_libchk (was Re: gvfs on FreeBSD 10 fails to build) Message-ID: <alpine.BSF.2.00.1311261113010.54550@wonkity.com> In-Reply-To: <CAN6yY1siA=s5AvCt8xAjzMu6%2B2DzT%2BagNQi%2BpFaqxtQZ-wwYKA@mail.gmail.com> References: <529453E6.3080200@gmail.com> <5294684E.1050105@passap.ru> <52946CE3.5010802@gmail.com> <5294757E.3010309@passap.ru> <CAN6yY1siA=s5AvCt8xAjzMu6%2B2DzT%2BagNQi%2BpFaqxtQZ-wwYKA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1311261113010.54550>