[Angstrom-devel] RFC: feed population policy

[Joshua Layne]

Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Joshua Layne schreef:
>   
>> Marcin Juszkiewicz wrote:
>>     
>
>   
>> My primary concern with this is space - I have a 40ish GB /home 
>> partition (small by today's standards, I know...) and I can only build 
>> two full sets without running a serious risk of filling my disk (one for 
>> my h2200 and one for my htctornado 
>>     
>
> Why? Angstrom supports multimachine, so you can build for all devices in
> a single tmpdir, which avoids duplication. On top of that you can use
> rm_work to remove the builddirs after the build. With that I can fit a
> multimachine build of over 30 machines into something like 14GByte.
>   
Does this handle things like gpephone, which require downrev versions of 
some packages?  I have 2 local.conf files that are selected based on the 
env-oe shell script that is provided on the gpephone wiki.
Although, I suppose that could be used just for 
machine/preferred-version selection and target the same tmp dir, which 
should be able to accommodate multiple versions of a package.

Does the rm_work option require a full rebuild every time you build?  
Unfortunately, that takes several days on my current system (a day and a 
half if nothing goes wrong, longer if I need to manually help the 
process)  One of the primary reasons that I have set up OE is to allow 
me to build other packages that I am interested in and have them neatly 
packaged up into ipk's - it seems like this requires a persistent work 
environment, but I may not understand it properly.

Thanks for the tip on this - it is quite likely that I am missing a few 
optimizations on my environment.

Regards,
josh