----- Le 14 Mar 16, à 11:15, Martin Jansa martin.ja...@gmail.com a écrit :
> On Sun, Mar 13, 2016 at 05:54:08PM -0400, Trevor Woerner wrote:
>> On 03/13/16 16:53, Paul Eggleton wrote:
>> > On Sun, 13 Mar 2016 16:42:41 Trevor Woerner wrote:
>> >> That's the problem I'm trying to solve: how can I easily keep all the
>> >> information required to reproduce this build, exactly. The whole "two
>> >> meta's" thing was just a speed bump.
>> >
>> > Right, understood, and it does make sense. I'm convinced there is an
>> > underlying problem to fix that this just papers over though.
>>
>> Okay, I think I see your point, and I agree. There is a layer clone
>> problem that should be addressed.
>>
>> But again, I think this is a speed bump.
>>
>> My underlying point is that we're purposefully leaving out information
>> that is vital to reproducible builds.
>
I think there are two problems here and that they need to be solved
separately...
* buildhistory does not save all the information to do a reproducible build
I think the easiest way to solve that would be to save the whole bitbake
environement used for building the recipe in the buildhistory. We would
loose the layout info (i.e what layer touched what variable, though that
info is in bitbake -e) but we would have enough info to reproduce the
build itself. Moreover being able to diff the environement would be
a great way to figure out what the change in the build actually was
* We need a way to easily transmit a set of meta revisions + extra info
that is a different problem, telling a user how to reproduce a build
from scratch, i.e starting from the download of the right meta. This
calls for a tool similar to repo, but adapted to yocto (which might
be repo itself, I don't know repo well enough to judge). What i've
seen so far is that most board vendors will ship an ugly shell
script that will clone and set the meta for you, usually doing some
ugly hacks like patching the meta themselves. Having an "official"
way to pack/distribute that info in yocto would be a very usefull
tool indeed
my 2 cents...
Cordialement
Jérémy Rosen
+33 (0)1 42 68 28 13
fight key loggers : write some perl using vim
Open Wide Ingenierie
23, rue Daviel
75013 Paris - France
www.openwide.fr
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
