All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: RFC: Rapid iterative development
Date: Fri, 19 Nov 2010 15:14:14 -0800	[thread overview]
Message-ID: <4CE704C6.6010203@linux.intel.com> (raw)

While working on a single package, I need to be able to tweak a variable 
in the new recipe, change the MACHINE in local.conf, etc. I'd like to be 
able to rapidly test my changes, but some of these changes trigger a 
long list of dependencies for various commands. While working on a new 
linux kernel recipe, I found it rebuilding a number of things that were 
either -native (can I force it to use the system version rather than 
building one) or seemed unrelated to the process at hand.

Are there some best practices for iterative recipe development that 
speed things along?

Thanks,

-- 
Darren Hart
Yocto Linux Kernel


             reply	other threads:[~2010-11-19 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 23:14 Darren Hart [this message]
2010-11-19 23:42 ` RFC: Rapid iterative development Tian, Kevin
2010-11-20  0:06   ` Darren Hart
2010-11-22 13:48 ` Joshua Lock

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=4CE704C6.6010203@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.