Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 Jul 2014 13:26:40 +0200
From:      John Marino <freebsd.contact@marino.st>
To:        Tijl Coosemans <tijl@FreeBSD.org>, John Marino <marino@FreeBSD.org>
Cc:        svn-ports-head@freebsd.org, kwm@FreeBSD.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org
Subject:   Re: svn commit: r362304 - head/x11-toolkits/pango
Message-ID:  <53CBA770.2010409@marino.st>
In-Reply-To: <20140720132259.156d687e@kalimero.tijl.coosemans.org>
References:  <201407200815.s6K8FG8b003096@svn.freebsd.org> <20140720132259.156d687e@kalimero.tijl.coosemans.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7/20/2014 13:22, Tijl Coosemans wrote:
> On Sun, 20 Jul 2014 08:15:16 +0000 (UTC) John Marino wrote:
>> Author: marino
>> Date: Sun Jul 20 08:15:16 2014
>> New Revision: 362304
>> URL: http://svnweb.freebsd.org/changeset/ports/362304
>> QAT: https://qat.redports.org/buildarchive/r362304/
>>
>> Log:
>>   x11-toolkits/pango: require explicit linking
>>   
>>   This new configure argument will list all required libraries in the
>>   generated pkgconf files.  Before any library indirectly pulled in, such
>>   as libm, was not listed.
>>   
>>   This fixes numerous regression in dports and it's more correct anyway.
> 
> No, this is wrong.  Each port should link to the libraries it needs on
> its own.  No port should rely on other ports to pull in libraries for
> them.

Then I guess we really don't need pkgconfig .pc files at all then?
(This is the point of .pc files, it tells how to link.  libm is directly
used by pango)

so no, it is not wrong.  The generated pc file was wrong, now it's not.
 This is why the configuration argument exists.



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