Re: [PATCH 2/2] doc/user_manual: Update after images per machine separation

[Jan Kiszka <jan.kiszka@siemens.com>]

On 12.03.19 21:27, Maxim Yu. Osipov wrote:
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
>   RECIPE-API-CHANGELOG.md | 23 +++++++++++++---
>   doc/user_manual.md      | 72 +++++++++++++++++++++++++------------------------
>   2 files changed, 57 insertions(+), 38 deletions(-)
> 
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index 197ce99..92f5dce 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -96,14 +96,14 @@ layer version higher than existing release corename, use the value 'next'.
>   
>   ### location of image artifacts
>   
> -Align with OpenEmbedded and place image artifacts in a per-machine folder placed
> +Align with OpenEmbedded and place image artifacts in a per-machine directory placed
>   in tmp/deploy (to avoid collisions among other things).
>   
>   ### more consistent artifact names
>   
>   multiconfig image artifacts are all placed in tmp/deploy/images. They include
>   kernel, initrd and ext4/wic images. A consistent naming scheme is now used:
> -`IMAGE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images
> +`IMAGE-MACHINE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images

Reading this again: Where does the first MACHINE in this file name come from? 
Maybe it can be avoided, now that we officially name image recipes after the 
machine.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux