On Wed, Dec 21, 2011 at 11:33 AM, Chris Larson wrote:
>>> problem with the := + oe_filter_out method is that it forces an
>>> immediate variable expansion right there, which can cause problems in
>>> some cases.
>>
>> Right. That and using it in a .conf file results in parsing errors. :-)
>
> := i
On 12/21/2011 09:33 AM, Chris Larson wrote:
> On Wed, Dec 21, 2011 at 9:10 AM, Darren Hart wrote:
>> On 12/21/2011 07:52 AM, Chris Larson wrote:
>>> On Wed, Dec 21, 2011 at 2:02 AM, Darren Hart wrote:
For example, I could not discover a way to use
oe_filter_out inside poky-tiny.conf t
On Wed, Dec 21, 2011 at 9:10 AM, Darren Hart wrote:
> On 12/21/2011 07:52 AM, Chris Larson wrote:
>> On Wed, Dec 21, 2011 at 2:02 AM, Darren Hart wrote:
>>> For example, I could not discover a way to use
>>> oe_filter_out inside poky-tiny.conf to remove "keyboard" for
>>> MACHINE_FEATURES.
>>
>>
On 12/21/2011 07:52 AM, Chris Larson wrote:
> On Wed, Dec 21, 2011 at 2:02 AM, Darren Hart wrote:
>> For example, I could not discover a way to use
>> oe_filter_out inside poky-tiny.conf to remove "keyboard" for
>> MACHINE_FEATURES.
>
> This might be best handled via inclusion of a .inc which
On Wed, Dec 21, 2011 at 2:02 AM, Darren Hart wrote:
> For example, I could not discover a way to use
> oe_filter_out inside poky-tiny.conf to remove "keyboard" for MACHINE_FEATURES.
This might be best handled via inclusion of a .inc which defines an
event handler or anonymous python function that
Poky-tiny defines a new distro policy for building tiny Linux images.
Rather than create new image tasks and recipes, it reuses existing ones,
modifying them as necessary. I believe it defines policy appropriate for
the distribution, but I'd welcome feedback regarding the distro/image split.
Please
