On Thu, Aug 30, 2012 at 3:41 AM, Michał Górny wrote:
> On Wed, 29 Aug 2012 19:12:01 -0400 Mike Frysinger wrote:
>> On Wed, Aug 29, 2012 at 6:37 PM, Ciaran McCreesh wrote:
>> > On Wed, 29 Aug 2012 18:18:20 -0400 Mike Frysinger wrote:
>> >> does it actually ? are DEPEND variables not allowed to be
>> >> expanded in pkg_* src_* funcs ?
>> >
>> > Nope. We don't guarantee that the metadata variable gets exported
>> > back to the ebuild environment.
>>
>> it's not a requirement, so if the PM doesn't export it, that's not a
>> problem.
>>
>> if [[ ${DEPEND+set} == "set" ]] && ! has virtual/pkgconifg
>> ${DEPEND} ; then eqawarn "..."
>> fi
>
> It may have a semi-random value, I think. Then you could warn for
> perfectly valid ebuilds.
in my quick test it seemed to have a fine value. let's deploy it and
see what kind of reports we get back.
you could also make it do:
libs=$("${pkgconf}" --libs "${tf}") || die
-mike