From: Phil Blundell <pb@pbcl.net>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] image.bbclass: Don't mark do_rootfs and do_build as nostamp
Date: Fri, 26 Apr 2013 12:30:38 +0100 [thread overview]
Message-ID: <1366975838.14512.99.camel@phil-desktop.brightsign> (raw)
There doesn't appear to be any compelling reason for these tasks to be nostamp
and having them re-run on every build can be irritating (for example, when the
image is an initramfs which your kernel image depends on).
Signed-off-by: Phil Blundell <philb@gnu.org>
---
meta/classes/image.bbclass | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ffb372a..667d03d 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -168,11 +168,9 @@ LINGUAS_INSTALL ?= "${@" ".join(map(lambda s: "locale-base-%s" % s, d.getVar('IM
PSEUDO_PASSWD = "${IMAGE_ROOTFS}"
-do_rootfs[nostamp] = "1"
do_rootfs[dirs] = "${TOPDIR} ${WORKDIR}/intercept_scripts"
do_rootfs[lockfiles] += "${IMAGE_ROOTFS}.lock"
do_rootfs[cleandirs] += "${S} ${WORKDIR}/intercept_scripts"
-do_build[nostamp] = "1"
# Must call real_do_rootfs() from inside here, rather than as a separate
# task, so that we have a single fakeroot context for the whole process.
--
1.7.10.4
next reply other threads:[~2013-04-26 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 11:30 Phil Blundell [this message]
2013-04-27 8:34 ` [PATCH] image.bbclass: Don't mark do_rootfs and do_build as nostamp Paul Eggleton
2013-04-27 9:08 ` Richard Purdie
2013-04-27 9:20 ` Koen Kooi
2013-04-29 14:45 ` Paul Eggleton
2013-04-29 14:54 ` Richard Purdie
2013-04-29 18:33 ` Phil Blundell
2013-05-02 18:05 ` Saul Wold
2013-04-27 9:24 ` Phil Blundell
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=1366975838.14512.99.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--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