<div>That sounds better option but we still will need a fallback there is a libfakedatetime as well which can be used to generate consistent date and time </div><div><br><div class="gmail_quote"><div>On Wed, Apr 26, 2017 at 10:52 AM Martin Jansa <<a href="mailto:martin.jansa@gmail.com">martin.jansa@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>What about passing the seed value (currently created based on last commit in repo you're building from - which doesn't need to be oe-core repository right?) to make it easier for people to pass whatever value works for them? even some constant value in DISTRO config.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 26, 2017 at 6:43 PM, Bystricky, Juro <span><<a href="mailto:juro.bystricky@intel.com" target="_blank">juro.bystricky@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> But not for 2 different builds with slightly modified metadata (e.g.<br>
> just because top commit is different in whatever build repository you're<br>
> running from even when it doesn't have any effect in your image), right?<br>
><br>
<br>
</span>This may be addressed in the future. Presently, the goal is to ensure that if we<br>
use identical repositories we get identical results. This should not depend<br>
on the time/date, build folder or even Linux distro. By identical results<br>
I mean binary identical comparison of the resulting "deploy" folders.<br>
(images, packages, licenses). So for example, there should be no binary differences<br>
between the two images of core-image-minimal.rootfs.ext4.<br>
In your case (slightly different repos), the difference would be presented<br>
as different time stamps for /etc/version and /etc/timestamp only.<br>
<span><br>
<br>
> So it doesn't fix the files-in-image.txt differences as described in:<br>
> <a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=5866" rel="noreferrer" target="_blank">https://bugzilla.yoctoproject.org/show_bug.cgi?id=5866</a><br>
><br>
<br>
</span>Eventually it will. There is still ways to go and this patch set is just the first<br>
kick at the can.<br>
<br>
<br>
</blockquote></div><br></div>
--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div></div>