From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] wget.py: use BPN when parsing upstream directory paths
Date: Thu, 03 Sep 2015 16:48:42 +0100 [thread overview]
Message-ID: <1441295322.24871.122.camel@linuxfoundation.org> (raw)
In-Reply-To: <6cc60f518992d5c20164cde35a3862edebdab385.1441294533.git.alexander.kanavin@linux.intel.com>
On Thu, 2015-09-03 at 18:37 +0300, Alexander Kanavin wrote:
> PN in this context may contain bogus suffixes like -native etc.
This is not that simple sadly. Bitbake has no knowledge of BPN, not
should it have really :/. This suggests we have a bit of an API
problem...
At the very least we should fallback to PN here is BPN isn't set.
Cheers,
Richard
prev parent reply other threads:[~2015-09-03 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1441294533.git.alexander.kanavin@linux.intel.com>
2015-09-03 15:37 ` [PATCH 1/1] wget.py: use BPN when parsing upstream directory paths Alexander Kanavin
2015-09-03 15:48 ` Richard Purdie [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=1441295322.24871.122.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=bitbake-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