Re: local apt repo cache not working as documented

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

On 28.11.18 10:00, Baurzhan Ismagulov wrote:
> Hello Henning,
> 
> On Tue, Nov 27, 2018 at 10:45:02AM +0100, Henning Schild wrote:
>> there is one more issue with that feature. The image you get will
>> contain an invalid sources.list and will not be "apt-get update"-able,
>> unlike the one we just "rebuild".
> 
> Do I understand correctly, you suggest to replace the local URI we bootstrapped
> from with the upstream URI from meta-isar/conf/distro/<something>.list?
> 
> I agree that the local URI isn't of much use on the target (unless one
> NFS-mounts the local repo), but I think that either variant is an arbitrary
> product policy that won't fit every product. If they target reproducibility, it
> isn't going to be a Debian URI anyway (if apt is to be used at all).
> 
> That said, for meta-isar -- which is a playground -- that would be convenient
> for the user. Feel free to submit a patch.

It's a default feature for images based on isar-image.bbclass that apt-get 
install works if the target has online connectivity. That should not be 
destroyed. It's actually exploited downstream (jailhouse-images, xenomai-images, 
and even at least one upcoming product).

Allowing to overwrite which repos should be used or even to remove packaging 
from the target completely are additional features on top.

Jan

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