Re: [yocto] coding style: hardcoding package names instead of using PN/BPN/etc

2013-11-04 Thread Paul Eggleton
On Saturday 02 November 2013 05:14:10 Robert P. J. Day wrote: i figure the answer is obvious but i'll ask it anyway -- is it reasonable to encourage new developers to use the general packagename variables such as PN and BPN rather than hardcoding packagenames in their recipe files?

Re: [yocto] coding style: hardcoding package names instead of using PN/BPN/etc

2013-11-03 Thread Khem Raj
On Sat, Nov 2, 2013 at 2:14 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel = 1 gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel-general = 1 gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel-video = 1 gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel-vaapi = 1 i'm *assuming*

[yocto] coding style: hardcoding package names instead of using PN/BPN/etc

2013-11-02 Thread Robert P. J. Day
i figure the answer is obvious but i'll ask it anyway -- is it reasonable to encourage new developers to use the general packagename variables such as PN and BPN rather than hardcoding packagenames in their recipe files? typically, you see things like this in recipe files: ALLOW_EMPTY_${PN}