From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC One recipe with two git repository as sources
Date: Thu, 23 Jun 2011 12:21:59 +0100 [thread overview]
Message-ID: <1308828119.21613.138.camel@phil-desktop> (raw)
In-Reply-To: <4E03211B.40205@freyther.de>
On Thu, 2011-06-23 at 13:18 +0200, Holger Freyther wrote:
> - destdir = os.path.join(destdir, "git/")
> + destsuffix = ud.parm.get("destsuffix", "git/")
> + print destsuffix
> + destdir = os.path.join(destdir, destsuffix)
I think that "print" might be extraneous, but other than this your patch
looks awesome. I think this would resolve the problem that I was having
in
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-June/004375.html and to which I never found a solution which didn't involve patching bitbake.
p.
next prev parent reply other threads:[~2011-06-23 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 11:18 RFC One recipe with two git repository as sources Holger Freyther
2011-06-23 11:21 ` Phil Blundell [this message]
2011-06-23 11:36 ` Holger Freyther
2011-06-23 14:25 ` Phil Blundell
2011-06-23 14:37 ` Mark Hatle
2011-06-23 14:37 ` Koen Kooi
2011-07-01 13:37 ` Holger Freyther
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=1308828119.21613.138.camel@phil-desktop \
--to=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox