Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Christopher Larson <clarson@mvista.com>
Subject: Re: [PATCH] bitbake.conf: rework FILESPATH generation.
Date: Thu, 19 Feb 2009 19:06:02 -0500	[thread overview]
Message-ID: <20090220000602.GE22652@denix.org> (raw)
In-Reply-To: <A1953057-56C2-4B3D-BF40-9778AC3D9139@mvista.com>

On Thu, Feb 19, 2009 at 04:58:25PM -0700, Christopher Larson wrote:
>
> On Feb 19, 2009, at 4:41 PM, Denys Dmytriyenko wrote:
>
>> On Thu, Feb 19, 2009 at 04:28:52PM -0700, Chris Larson wrote:
>>> From: Chris Larson <clarson@mvista.com>
>>>
>>> Rework FILESPATH generation to be done in bitbake.conf, avoiding the
>>> confusion about it being in multiple places.  Adds FILESPATHBASE and
>>> FILESPATHPKG which can be manipulated rather than manipulating FILESPATH
>>> directly.
>>>
>>> One usage possibility:
>>>
>>> FILESPATHBASE =. "${TOPDIR}/files:"
>>>
>>> Which would let me provide a custom busybox config for this build by
>>> copying the defconfig from the openembedded metadata into my
>>> build/files/busybox-1.0/ directory, for example.
>>
>> Can you please provide more details on this example? Thanks.
>
> Normally, all paths in FILESPATH are relative to FILE_DIRNAME, the location 
> of the recipe being operated against.  With this change, you can place 
> files which are in SRC_URI as file:// urls in paths relative to other 
> locations.
>
> You can do package customizations via changes to file:// files without 
> mucking up the local clone of the openembedded repository.
>
> 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.
>
> Does that answer your question?

That would be a very welcome addition! Thanks.

-- 
Denys



  parent reply	other threads:[~2009-02-20  0:08 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 [this message]
2009-02-20  0:27   ` Chris Larson
2009-02-20  0:58     ` Tom Rini
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=20090220000602.GE22652@denix.org \
    --to=denis@denix.org \
    --cc=clarson@mvista.com \
    --cc=openembedded-devel@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