All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: FILESPATHPKG question
Date: Wed, 06 May 2009 14:18:18 -0400	[thread overview]
Message-ID: <4A01D46A.4030904@balister.org> (raw)
In-Reply-To: <b6ebd0a50905061111x4bcc369dr91909b50e4b9268@mail.gmail.com>

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

Chris Larson wrote:
> On Wed, May 6, 2009 at 10:57 AM, Philip Balister <philip@balister.org> wrote:
>> Phil Blundell wrote:
>>> On Wed, 2009-05-06 at 09:54 -0400, Philip Balister wrote:
>>>> +FILESPATHPKG = "u-boot-git:u-boot:files:."
>>>> Ignore the added patch :) Should I go ahead and push the FILESPATHPKG
>>>> change? Otherwise all the patches will end up in the files directory ....
>>> Wouldn't you be better off just prepending to FILESPATHPKG rather than
>>> replacing it?  As in, FILESPATHPKG =. "u-boot-git:" or something.
>> I'd taken from a similar patch for uclibc. (That needs acks or comments).
>>
>> What's the difference between =+ ad =.? Both work and I see more of the =+
>> form?
> 
> The + operations insert a space separator.  The FILESPATH vars use :
> as their separator, not +, so no, they don't "Both work".

Theoretically you might be correct :)

But,

FILESPATHPKG =+ "u-boot-git:"

is working for me. I'll push the =. form in case this changes in the 
future. I want to make sure I understand what is going on so we can get 
the most correct fixes in.

Could someone also look at the uclibc patch for this sort of thing?

http://patchwork.openembedded.org/patch/436/

Philip

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

      reply	other threads:[~2009-05-06 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 13:54 FILESPATHPKG question Philip Balister
2009-05-06 16:07 ` Phil Blundell
2009-05-06 17:57   ` Philip Balister
2009-05-06 17:27     ` Phil Blundell
2009-05-06 18:11     ` Chris Larson
2009-05-06 18:18       ` Philip Balister [this message]

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=4A01D46A.4030904@balister.org \
    --to=philip@balister.org \
    --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 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.