<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 27, 2014 at 10:49 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Thu, 2014-03-27 at 10:21 -0700, Chris Larson wrote:<br>
><br>
> On Mon, Mar 24, 2014 at 8:10 PM, Robert Yang<br>
> <<a href="mailto:liezhi.yang@windriver.com">liezhi.yang@windriver.com</a>> wrote:<br>
> If we run "bitbake -S base-files" today, and re-run it<br>
> <span class="aBn" tabindex="0"><span class="aQJ">tomorrow</span></span> with<br>
> nothing changed, we would see that the do_install.sigdata<br>
> changes<br>
> because of:<br>
><br>
> do_intall -> do_install_basefilesissue -> DISTRO_VERSION -><br>
> DATE<br>
><br>
> We had set:<br>
> IMAGE_NAME[vardepsexclude] += "DATETIME"<br>
> in meta/conf/bitbake.conf, we can set a similar line in<br>
> <a href="http://base-files_3.0.14.bb" target="_blank">base-files_3.0.14.bb</a> to fix the problem.<br>
><br>
> [YOCTO #6032]<br>
><br>
> Signed-off-by: Robert Yang <<a href="mailto:liezhi.yang@windriver.com">liezhi.yang@windriver.com</a>><br>
><br>
> Wont't this mean base-files wouldn't be rebuilt when the day changes?<br>
> This seems problematic to me. I think this is a legitimate case for a<br>
> checksum change. If the distro version changes due to the date<br>
> changing, and the base-files includes the distro version in the issue<br>
> file, then we'd *want* base-files to rebuild to ensure the issue file<br>
> is correct, otherwise it'd be inaccurate, no?<br>
><br>
</div>I'm torn on this. Package feed creators probably don't want a package<br>
feed where the package changes daily but I can see this from both sides,<br>
I have often wondered why my build was rebuilding base-files...</blockquote></div><br>Perhaps we should either not use DATE/TIME in the distro version at all, or have a variable which is the current date, and a variable which locks to the date of the creation of the TMPDIR but doesn't change after that, or something, as a more persistent build environment identifier to use for such cases. *shrug*<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>