Re: [PATCH] added 'isar-cfg-userpw' package

[Claudius Heine <claudius.heine.ext@siemens.com>]

Hi,

On 25/02/2019 12.44, Claudius Heine wrote:
> Quoting Jan Kiszka (2019-02-25 12:15:32)
>> On 25.02.19 10:32, Henning Schild wrote:
>>> Am Mon, 25 Feb 2019 09:48:38 +0100
>>> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
>>>> On 25.02.19 09:44, Claudius Heine wrote:
> [...]
>>>>> But of course if you now have a '*-debug' and '*-release'
>>>>> multiconfig, you cannot build that in parallel if one package is
>>>>> build with two different variables.
>>>>>
>>>>> And that exactly hits the mark with the problem I have with the way
>>>>> Isar uses multiconfigs and tries to share packages from different
>>>>> multiconfigs.
>>>>>
>>>>> IMO if you want to continue doing it that way, you would need to
>>>>> have a 'isar-cfg-localpurge-debug' and a 'isar-cfg-userpw-debug'.
>>>>> And do that for all possible other configurations you want to build
>>>>> in parallel...
>>>>
>>>> Awkward. We need to stop this weird patterns which require too much
>>>> boilerplate recipes to achieve very simple things. Let's just make
>>>> these variables per-image.
>>>
>>> I had a feeling that same PN-PV but different content could be a
>>> problem. And here we go. But Claudius is right, either we have
>>> different packages (by name and/or version) or we do not use packages
>>> for such tasks. Per Image variables will not work, the last
>>> do_deploy_deb will win and set the password for every image sharing the
>>> repo.
>>
>> Right, we need to discuss about that "everything is a package" in this context.
>> I may make Isar life easier, but not Isar user's life. Also, it's deviating with
>> the image configuration from OE.
> 
> I now took a look exactly how OE manage that, and that seems to answer
> my previous question. The implementation seems a bit complex, but I
> guess that it could be adapted to fit Isars purposes.

Well the exact implementation in OE might be a bit to much, since that 
is part of meta/lib/oe/rootfs.py and that leads down into a rabbit hole 
very fast.

So that will have to be implemented mostly new for Isar.

regards,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de