Re: [PATCH 0/3] use local repo for multistrap and drop "dpkg -i"

[Baurzhan Ismagulov <ibr@radix50.net>]

On Fri, Aug 11, 2017 at 10:13:46AM +0200, Henning Schild wrote:
> > Regarding the increase of build time, I'd really like to avoid that.
> 
> Me too, that is why i started the discussion on caching. Giving up on
> the gatekeeper idea would IMHO not be the way to go.
> 
> > Building all configurations in one run already takes up to 40 min.
> 
> CI is patient and for basic testing one does not need to build all of
> them.

I'm not patient ;) , since I test every commit during every rebase... We should
automate that, too. But even then, build time will still be developer time.
Performance is the last but not the least requirement.


> > The problem should be easily mitigatable by splitting rootfs
> > multistrap and apt-getting the built packages into separate recipes.
> 
> Yes but that is what i mean with "giving up the gatekeeper". We could
> implement both ways controlled by a variable in a config. That would
> speed up the builds during development and allow switching to strict
> gatekeeper mode for releases.

What is the disadvantage of splitting into two recipes? An image would still
require apt-get install, so this step would not be omitted. Implemented in this
way, the second recipe would be your gatekeeper, no?

Adding one boolean variable doubles the amount of testing required. It's
configuration permutations that kill. That is why I'd prefer settling on one
way.


With kind regards,
Baurzhan.