[OE-core] [PATCH] doc: drop some incorrect instructions

Ming Liu liu.ming50 at gmail.com
Wed Nov 14 19:47:14 UTC 2018


Hi, Scott:

Thanks for the re-writing, I think it's correct technically, the incorrect
description had been removed.

//Ming Liu

Scott Rifenbark <srifenbark at gmail.com> 於 2018年11月14日 週三 下午8:36寫道:

> Ming,
>
> I could not simply apply this patch.  I had to do some re-writing for
> clarity.  Please look at this link to the updated section on the
> image_types class and let me know if this is technically correct.
>
>
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#ref-classes-image_types
>
> Thanks,
> Scott
>
> On Wed, Nov 14, 2018 at 11:06 AM <liu.ming50 at gmail.com> wrote:
>
>> From: Ming Liu <liu.ming50 at gmail.com>
>>
>> image_types bbclass now is being inherited mandatorily in image.bbclass
>> through the variable IMGCLASSES, and the users do not have to inherit
>> it in their customized image type bbclass, or put it in IMAGE_CLASSES.
>>
>> Drop the incorrect descriptions, it's confusing the developers.
>>
>> Signed-off-by: Ming Liu <liu.ming50 at gmail.com>
>> ---
>>  documentation/ref-manual/ref-classes.xml | 9 ++-------
>>  1 file changed, 2 insertions(+), 7 deletions(-)
>>
>> diff --git a/documentation/ref-manual/ref-classes.xml
>> b/documentation/ref-manual/ref-classes.xml
>> index 24d7a0a..876e242 100644
>> --- a/documentation/ref-manual/ref-classes.xml
>> +++ b/documentation/ref-manual/ref-classes.xml
>> @@ -1275,15 +1275,10 @@
>>      </para>
>>
>>      <para>
>> -        By default, this class is enabled through the
>> -        <link
>> linkend='var-IMAGE_CLASSES'><filename>IMAGE_CLASSES</filename></link>
>> -        variable in
>> +        By default, this class is enabled mandatorily in
>>          <link
>> linkend='ref-classes-image'><filename>image.bbclass</filename></link>.
>>          If you define your own image types using a custom BitBake class
>> and
>> -        then use <filename>IMAGE_CLASSES</filename> to enable it, the
>> custom
>> -        class must either inherit <filename>image_types</filename> or
>> -        <filename>image_types</filename> must also appear in
>> -        <filename>IMAGE_CLASSES</filename>.
>> +        then use <filename>IMAGE_CLASSES</filename> to enable it.
>>      </para>
>>
>>      <para>
>> --
>> 2.7.4
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20181114/c8232647/attachment-0001.html>


More information about the Openembedded-core mailing list