Re: [PATCH 1/6] meta/dpkg: Make 'do_unpack' more generic, prepare for pulling out

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

On 2017-09-04 17:11, Alexander Smirnov wrote:
> On 08/30/2017 10:03 PM, Henning Schild wrote:
>> Issue:
>> The unpacker in dpkg is not generic since it does not unpack to
>> WORKDIR, so it can not be pulled into a more generic class to make it
>> available for other users.
>>
> 
> As I already wrote to mail-list, WORKDIR and BUILDROOT are different
> folders, and there was the reason to do so.
> 
> In Yocto, WORKDIR is the place which keeps the following artifacts:
> 
>  - Source code tree
>  - Patches, configs
>  - Binaries
>  - Yocto meta information (logs and build commands)
> 
> WORKDIR is usually something like: ./tmp/work/gcc-arch/package-name
> 
> Due to Yocto performs cross-compilation, it is able to keep source core
> out of cross filesystem. But this doesn't work for Isar, which uses
> 'native' compilation in chroot. That's why BUILDROOT variable was
> introduced.
> 
> So in Isar, WORKDIR stays the same and keeps logs, build commands,
> patches and other stuff (for example configs and scripts for
> buildchroot). The BUILDROOT is the path to dedicated buildchroot where
> to unpack sources and build them.

That should probably go into your design doc, even more as it deviates
from OE practice.

> 
> If I build multiconfig for N targets with this patch, I will have N
> distributed locations with bitbake meta information for the same package.
> 
> If I cleanall buildchroot, I will lose all the bitbake meta information
> for current distro-arch.
> 
> So at the moment I don't see any benefit of this change.
> 
> Also it's not clear, what do you mean by 'not generic', this unpack
> implementation designed for building deb packages, and at the moment no
> other users are expected.
> 

I suppose many misunderstandings come from the fuzziness that
multiconfig introduces. That requires documentation, even more as it is
easy to break and then fairly hard to diagnose.

How does OE deal with multiconfig requirements on recipes? Or don't they
have the complication?

Jan

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