FILESPATHPKG question

[Philip Balister <philip@balister.org>]

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

I ran across the change in files path behavior today. I'm trying to test 
a beagleboard specific mux config in u-boot and was having trouble 
figuring out where the patch should go.

To get it to live in u-boot-git/beagleboard/foo.patch I made the 
following change to the u-boot_git.bb recipe:

diff --git a/recipes/u-boot/u-boot_git.bb b/recipes/u-boot/u-boot_git.bb
index 9846cd8..a133532 100644
--- a/recipes/u-boot/u-boot_git.bb
+++ b/recipes/u-boot/u-boot_git.bb
@@ -1,6 +1,8 @@
  require u-boot.inc
  PR ="r22"

+FILESPATHPKG = "u-boot-git:u-boot:files:."
+
  SRC_URI = "git://www.denx.de/git/u-boot.git;protocol=git "
  SRCREV_davinci-sffsdr = "4b50cd12a3b3c644153c4cf393f4a4c12289e5aa"
  SRCREV_davinci-dvevm = "4b50cd12a3b3c644153c4cf393f4a4c12289e5aa"
@@ -12,6 +14,7 @@ SRCREV_afeb9260 = 
"2077e348c2a84901022ad95311b47b70361e6daa"
  SRC_URI_beagleboard = 
"git://gitorious.org/u-boot-omap3/mainline.git;branch=omap3-dev;protocol=git 
\
                   file://fw-env.patch;patch=1 \
                   file://dss2.patch;patch=1 \
+                 file://mcspi3-mux.patch;patch=1 \
  "
  SRCREV_beagleboard = "2dea1db2a3b7c12ed70bbf8ee50755089c5e5170"
  PV_beagleboard = "2009.03+${PR}+gitr${SRCREV}"

Ignore the added patch :) Should I go ahead and push the FILESPATHPKG 
change? Otherwise all the patches will end up in the files directory ....

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]