On Wed, Mar 25, 2015 at 01:31:31PM -0700, Janne Karhunen wrote:
> Hi,
>
> Thanks, inherited that file and missed that - and my RPM legacy was
> thinking that's about right.
>
> How do you guys test people don't leak dependencies with global
> DEPENDS? Even this must have been passing by accident
Hi,
Thanks, inherited that file and missed that - and my RPM legacy was
thinking that's about right.
How do you guys test people don't leak dependencies with global
DEPENDS? Even this must have been passing by accident quite a while :)
--
Janne
On Wed, Mar 25, 2015 at 11:30 AM, Martin Jansa w
On Wed, Mar 25, 2015 at 10:39:34AM -0700, Janne Karhunen wrote:
> Hi,
>
> Wonder if you guys can share some insights on how to debug this case.
> I have a legacy PAM module recipe that says:
>
> DEPENDS_${PN} = "libpam"
>
> 'pam' is listed in DISTRO_FEATURES and is working fine. However, for
> t
Hi,
Wonder if you guys can share some insights on how to debug this case.
I have a legacy PAM module recipe that says:
DEPENDS_${PN} = "libpam"
'pam' is listed in DISTRO_FEATURES and is working fine. However, for
that pam module libpam dependency is silently dropped during the
build. If PAM happ
