Re: dev manual section on "customizing images" needs serious adjustment

[Tomas Frydrych <tf+lists.yocto@r-finger.com>]

On 24/08/12 16:45, Robert P. J. Day wrote:
> On Fri, 24 Aug 2012, Scott Garman wrote:
> 
>> On 08/23/2012 01:13 AM, Tomas Frydrych wrote:
>>> Hi,
>>>
>>> On 22/08/12 21:37, Robert P. J. Day wrote:
>>>> One way to get additional software into an image is to create a
>>>> custom image.
>>>
>>> The manual should make it clear that this is *the* canonical way to add
>>> software to your images. Modifications to local.conf are temporary
>>> tweaks for testing/debugging (i.e., you should never feel the need to
>>> commit your local.conf to some project version control system).
>>>
>>> Tomas
>>
>> +1. If you add additional packages to core-image-minimal in your local.conf,
>> you're no longer really building core-image-minimal.
> 
>   sure.  but if you similarly explicitly set IMAGE_INSTALL before
> inheriting core-image, you're not really "inheriting" core-image
> either. :-)

That is quite a different thing: core-image-minimal is a recipe to build
an image with defined contents, in contrast core-image is a class, and
the whole point of classes is that recipes can inherit and override them.

Tomas