Re: [PATCH 3/4] build.sh: Update apt sources

[Alexander Smirnov <asmirnov@ilbers.de>]

On 02/01/2018 02:40 PM, Jan Kiszka wrote:
> On 2018-02-01 12:29, Alexander Smirnov wrote:
>> Trigger apt sources update before building the package to be sure that
>> we are in sync with isar-apt content.
>>
>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>> ---
>>   meta/recipes-devtools/buildchroot/files/build.sh | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh
>> index 77e0fdd..5c59193 100644
>> --- a/meta/recipes-devtools/buildchroot/files/build.sh
>> +++ b/meta/recipes-devtools/buildchroot/files/build.sh
>> @@ -3,6 +3,9 @@
>>   # This software is a part of ISAR.
>>   # Copyright (C) 2015-2017 ilbers GmbH
>>   
>> +# Make sure that we have latest isar-apt content
>> +apt-get update
>> +
> 
> Can we confine this to the isar-apt repo? Or is there no risk that an
> upstream repo update will result in a buildchroot change that is
> inconsistent with an earlier build stage?

That's a good point, I've already checked it, it seems to be possible like:

sudo apt-get update -o Dir::Etc::sourcelist="sources.list.d/${source}" \
-o Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="0"

[https://askubuntu.com/questions/65245/apt-get-update-only-for-a-specific-repository]

But I decided that it makes no sense, because target image will be 
generated later and use upstream apt. So if something has been changed 
during buildchroot operating, this will affect target image anyway.

Again I think this should be handled outside buildchroot by caching 
upstream apts.

Alex