From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] base-files: do_install.sigdata: remove the depends on DATE
Date: Thu, 27 Mar 2014 17:49:25 +0000 [thread overview]
Message-ID: <1395942565.24890.156.camel@ted> (raw)
In-Reply-To: <CABcZAN=NYQCRUR-hQR+yZK6L7OSaUj+cFyQu6EbvcqK_5fwZBQ@mail.gmail.com>
On Thu, 2014-03-27 at 10:21 -0700, Chris Larson wrote:
>
> On Mon, Mar 24, 2014 at 8:10 PM, Robert Yang
> <liezhi.yang@windriver.com> wrote:
> If we run "bitbake -S base-files" today, and re-run it
> tomorrow with
> nothing changed, we would see that the do_install.sigdata
> changes
> because of:
>
> do_intall -> do_install_basefilesissue -> DISTRO_VERSION ->
> DATE
>
> We had set:
> IMAGE_NAME[vardepsexclude] += "DATETIME"
> in meta/conf/bitbake.conf, we can set a similar line in
> base-files_3.0.14.bb to fix the problem.
>
> [YOCTO #6032]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>
> Wont't this mean base-files wouldn't be rebuilt when the day changes?
> This seems problematic to me. I think this is a legitimate case for a
> checksum change. If the distro version changes due to the date
> changing, and the base-files includes the distro version in the issue
> file, then we'd *want* base-files to rebuild to ensure the issue file
> is correct, otherwise it'd be inaccurate, no?
>
I'm torn on this. Package feed creators probably don't want a package
feed where the package changes daily but I can see this from both sides,
I have often wondered why my build was rebuilding base-files...
Cheers,
Richard
next prev parent reply other threads:[~2014-03-27 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 3:10 [PATCH 0/1] base-files: do_install.sigdata: remove the depends on DATE Robert Yang
2014-03-25 3:10 ` [PATCH 1/1] " Robert Yang
2014-03-27 17:21 ` Chris Larson
2014-03-27 17:49 ` Richard Purdie [this message]
2014-03-27 17:53 ` Chris Larson
2014-03-27 18:13 ` Martin Jansa
2014-03-27 18:31 ` Mark Hatle
2014-03-28 1:44 ` Robert Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395942565.24890.156.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox