[Toaster] Toaster] [RFC] Image customisation with Toaster

[Paul Eggleton]

On Wednesday 06 May 2015 10:25:45 Paul Eggleton wrote:
> On Wednesday 06 May 2015 09:11:57 Barros Pena, Belen wrote:
> > On 05/05/2015 20:07, "Lerner, Dave" <dave.lerner at windriver.com> wrote:
> > >Belen,
> > >
> > >> > Is it impractical to prebuild, then preload the database with package
> > >> >
> > >> >dependencies for a few standard oe images and downloadable bsps?
> > >> 
> > >> When would that 'prebuilding' happen? Can it be stopped? My worry is
> > >> about people just trying Toaster locally, in machines that are not very
> > >> powerful and can take ages to build things. If we need to do this
> > >> 'prebuilding' when you set up Toaster, and you cannot stop it once it's
> > >> started, that can cause trouble.
> > >
> > >By prebuilts, I meant that it would be done before release on a few major
> > >bitbake image targets for some selection of bsps during the yocto release
> > >build process, that is, by the yocto team.  This dependency list would be
> > >part of the yocto distribution that helps populate toaster tables.
> > 
> > I see. This sounds like a question for Paul Eggleton. We'll see what he
> > thinks.
> 
> It's certainly possible. The question would be whether or not this would be
> accurate and applicable enough to users who are changing their configuration
> before their first build. On the other hand you could argue that some
> results might be better than none.

I'm not sure if you have talked about this already, but FWIW we were planning 
on solving this in a manner which is more likely to incorporate the user's 
configuration by doing a parse. Whilst this won't give a complete picture of 
package-level dependencies it's at least the same picture that BitBake has 
before doing a build. With "pre-builts" there's no way to have a comprehensive 
coverage of all layers or incorporate any user configuration changes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre