From owner-freebsd-ports@FreeBSD.ORG Fri Jul 20 19:24:21 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id C58B2106564A; Fri, 20 Jul 2012 19:24:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A8D9314E0D1; Fri, 20 Jul 2012 19:24:20 +0000 (UTC) Message-ID: <5009B064.9080104@FreeBSD.org> Date: Fri, 20 Jul 2012 12:24:20 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Julien Laffaye References: <50098EEF.8040801@shatow.net> <1E76612CE817410FAA2CF925F9CC300A@Rivendell> <5009A876.2010905@freebsd.org> <5009AE6A.1040109@freebsd.org> In-Reply-To: <5009AE6A.1040109@freebsd.org> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Reko Turja , Kimmo Paasiala , freebsd-ports@freebsd.org Subject: Re: How to remove erroneous deps from pkgng X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 19:24:21 -0000 On 07/20/2012 12:15, Julien Laffaye wrote: > On 7/20/2012 9:03 PM, Kimmo Paasiala wrote: >> On Fri, Jul 20, 2012 at 9:50 PM, Julien Laffaye >> wrote: >>> On 7/20/2012 8:36 PM, Reko Turja wrote: >>>>> Its use is not limited to Gnome, as you can see it's used in the build >>>>> process of databases/sqlite3 and there are many other ports that have >>>>> nothing to do with Gnome that use it the same way. The only thing that >>>>> is wrong with it is that ends up being a run time dependency of >>>>> sqlite3 instead of being only a build time dependency. Maybe this >>>>> could be changed, anyone know if it's possible? >>>> >>>> Actually, sqlite3 builds and works quite fine with pkg-config >>>> dependency >>>> removed from makefile. So it's kinda silly to pull it in by force - of >>>> course it's not pkgng problem, but a problem in the port itself. >>> sqlite3 installs "/usr/local/libdata/pkgconfig/sqlite3.pc". >>> So I think the rationale is if a developper wants to link against >>> sqlite3 >>> using the pkg-config file, he should have pkg-config on his machine. >>> If you go this way, you could also ask why sqlite3 install header files >>> which are not needed for the runtime dependency (when what is >>> required is >>> only the shared object)... >>> >> This could be handled by having pkg-config only as a build time >> dependency for sqlite3 and for any port that depends on it, pkg-config >> is a build time tool much like autoconf, automake, libtool etc. and is >> not needed to use the port at run time. This is correct. > Yes it is needed at runtime if you are a developper using sqlite3 and > pkg-config: > to use `pkg-config sqlite3 --cflags` and `pkg-config sqlite3 --libs` in > your $APP build process. If you're developing a port, then the port needs to have a build dep on pkg-config. If you're developing your own stuff, then you need to install pkg-config as a build tool, just like you would (theoretically) install gmake, autoconf, etc. Run dependencies are for things that the installed package needs in order to *run*. Doug -- Change is hard.