All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Cc: Chris Larson <clarson@mvista.com>
Subject: Re: [PATCH] bitbake.conf: rework FILESPATH generation.
Date: Thu, 19 Feb 2009 17:58:05 -0700	[thread overview]
Message-ID: <20090220005805.GA5352@smtp.west.cox.net> (raw)
In-Reply-To: <b6ebd0a50902191627x48e60175o8f3e20e0a0bf2104@mail.gmail.com>

On Thu, Feb 19, 2009 at 05:27:34PM -0700, Chris Larson wrote:
[snip]
> My intent is to create a class to facilitate running make menuconfig
> on your kernel and busybox, and retain those changes.  Today, people
> either go into workdir and customize it there, but those changes are
> lost when you clean the package, or they overwrite files in the
> metadata repository, which can lead to conflicts, and is just all
> around more annoying to work with.  It's better to be able to have per
> build or site wide overrides of those files.

Playing the devils advocate here, conflicts make you go "Oh, I need to
see what happened", or at least should.  But so long as wherever this
gets documented emphasizes that people need to be aware what they're
doing (it's like setting up your own overlay, but not quite as
intensive) and need to keep an eye out when re-syncing with upstream, it
should certainly fix more headaches than it creates.

-- 
Tom Rini



  reply	other threads:[~2009-02-20  1:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 23:28 [PATCH] bitbake.conf: rework FILESPATH generation Chris Larson
2009-02-19 23:41 ` Denys Dmytriyenko
     [not found]   ` <A1953057-56C2-4B3D-BF40-9778AC3D9139@mvista.com>
2009-02-20  0:06     ` Denys Dmytriyenko
2009-02-20  0:27   ` Chris Larson
2009-02-20  0:58     ` Tom Rini [this message]
2009-02-20 11:24     ` Otavio Salvador

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=20090220005805.GA5352@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=clarson@mvista.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.