Re: [PATCH v4 0/4] Basic binary cache implementation

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

On 2017-10-04 10:32, [ext] Claudius Heine wrote:
> Hi,
> 
> On 10/0    '2/2017 05:45 PM, Alexander Smirnov wrote:
>> Hello everybody,
>>
>> this series introduces basic binary caching for Isar.
>>
>> There is a new layer: meta-isar-bin which is intended to be the binary
>> cache. All the packages that are built in Isar are stored in this
>> cache using reprepro.
>>
>> Having the separate layer makes possible to manage this cache separately
>> from the Isar build tree. So once you have built your packages, you could
>> re-use this cache for further builds.
> 
> We still have to talk about your requirement for the cache to be
> sharable and your resulting implementation of it as a meta layer.
> 
> Since I still don't see the benefit of a sharable cache and think that
> putting binary packages into some kind of strange meta layer is not the
> right solution and could potentially create more problems that is solves
> because its very much in conflict with the fundamental idea of a meta
> layer.

Indeed, state like this (disclaimer: i didn't look into all details), it
sounds like a weird architecture to me as well. Thinking of an artifact
cache, I would rather expect something like OE's sstate that one may
preserve across builds, share between devs, or whatever. If it's there,
the build system consults it, if not, it rebuilds. But sstate is not a
layer, for some good reasons.

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