AW: multistrap fails when aptsources not specified
-----Ursprüngliche Nachricht-----
Von: Neil Williams [mailto:codehelpmail@gmail.com] Im Auftrag von Neil Williams
Gesendet: Freitag, 8. Juli 2011 18:03
An: Debian Embedded
Betreff: Re: multistrap fails when aptsources not specified
> On Fri, 8 Jul 2011 13:12:06 +0200
> "Wachholz, Ruediger" <Ruediger.Wachholz@siemens-enterprise.com> wrote:
>
> > multistrap fails when aptsources is not specified within multistrap.conf:
>
> Please file a bug report (severity normal), the --simulate option
> should prevent that from being a problem.
OK.
>
> > As the embedded system i'm thinking of will not be allowed to be updated by apt
> > i think it should be valid not to specify any update repositories, isn't it?
>
> The aptsources will be a single file, two lines long. If you specify
> cleanup=true then the actual apt cache data will be removed, as will
> all the packages in /var/cache/apt/archives, so having a dummy apt
> sources list is not a burden to the system.
Thanks for the explanations, i'm sure it's easy to work around a "dummy" sources.list
(e.g. by removing it just before deploying it to the target).
Obviously omitting the aptsources parameter is not relevant for actual
users of multistrap as this problem has not been mentioned so far.
>
> Many embedded systems do still want to have apt available.
>
> > Or do i have a wrong understanding of aptsources?
>
> This is more the territory of Emdebian Baked - if you don't have apt,
> you need to consider why this choice is made:
>
> 0: You don't have space for apt - it isn't that large and the larger
> dependencies will likely be brought in by apt
>
> 1: If you remove apt for reasons of space, dpkg should also be removed
> for the same reasons but this is a lot harder to do
>
> 2: As above, to simply not let your space be taken up by
> the /var/lib/apt/lists and /var/cache/apt/pkgcache.bin, then just
> specify cleanup=true to multistrap.
apt will be installed during development but be removed from the
productive system if this can be done easily. dpkg will remain for
debug purposes. of course cache files will be removed.
Reply to: