From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] Fix the SDK generation
Date: Tue, 02 Aug 2011 14:34:21 +0100 [thread overview]
Message-ID: <1312292061.2344.591.camel@rex> (raw)
In-Reply-To: <cover.1312243899.git.mark.hatle@windriver.com>
On Mon, 2011-08-01 at 19:17 -0500, Mark Hatle wrote:
> This is an attempt to fix a number of issues with the SDK generation. It has been
> tested using bitbake meta-toolchain-sdk.
>
> Note, patches:
>
> 4/5: package_ipk: SDK generation workaround
> 5/5: update-alternatives: Add alternatives as a runtime provide
>
> 4/5 might be reasonable to implement immediately to resolve this issue.. However
> 5/5 is absolutely incorrect and that is noted within the patch header. I'd
> like comments on the issue to understand how to fix the problem.
I've merged 1-4 to master, 4 on the grounds that it improves the
situation substantially.
For 5, I suspect we'll need to process the path using python, I can't
really see a way to avoid it. I assume / is an illegal character for deb
anywhere, not just at the start of the dependency name?
Cheers,
Richard
prev parent reply other threads:[~2011-08-02 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 0:17 [PATCH 0/5] Fix the SDK generation Mark Hatle
2011-08-02 0:17 ` [PATCH 1/5] rootfs_rpm: Cleanup and minor bug fixes Mark Hatle
2011-08-02 0:17 ` [PATCH 2/5] bitbake.conf: Add SDK_PACKAGE_ARCHS Mark Hatle
2011-08-02 0:17 ` [PATCH 3/5] populate_sdk_*: Sync SDK and regular rootfs functions Mark Hatle
2011-08-02 0:17 ` [PATCH 4/5] package_ipk: SDK generation workaround Mark Hatle
2011-08-02 0:17 ` [PATCH 5/5] update-alternatives: Add alternatives as a runtime provide Mark Hatle
2011-08-02 13:46 ` Phil Blundell
2011-08-02 14:49 ` Mark Hatle
2011-08-03 12:20 ` Richard Purdie
2011-08-03 14:41 ` Mark Hatle
2011-08-03 15:40 ` Richard Purdie
2011-08-03 16:03 ` Mark Hatle
2011-08-03 16:09 ` Richard Purdie
2011-08-02 13:34 ` 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=1312292061.2344.591.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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