From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] x-load: add signGP to sourceipk
Date: Thu, 29 Jul 2010 19:41:54 +0200 [thread overview]
Message-ID: <i2seh2$mrf$1@dough.gmane.org> (raw)
In-Reply-To: <0d6a01cb2f30$47a0b040$d6e210c0$@Distant-earth.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29-07-10 17:11, John Willis wrote:
>> * When creating a source ipk for the x-load program copy the
>> signGP binary as well as this is needed when rebuilding.
>> * Bump the PR for x-load-omap3pandora recipe.
>>
>> Signed-off-by: Chase Maupin <chase.maupin@ti.com>
>
> Nack, this seems totally pointless, signGP is in the tree (signgp-native) so
> is it not better to bring that in?
>
> Out of interest, what is the problem you see with the current setup, the
> recipes as they stand will give people signed and unsigned X-Loader binaries
> for just about all purposes you could want them on the OMAP3. Or is this
> patch aimed at using source IPK's for use in another non-OE SDK?
>
> Shipping binaries in a source IPK seems very wrong regardless of the need,
> it's not really source at that point ;-).
What Chase actually needed was an -sdk package, so:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=962d52ae8358d8fd11ae8a7054fa785d102cf274
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMUb1iMkyGM64RGpERArLhAJoD27ERUKmy2OrmVZNK5kzEzVWi8QCgmIpZ
s2B/iRmjYI0hrFSLpiz9SBY=
=4MXC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-29 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 12:26 [PATCH 1/2] x-load_git: defined config for dm37x and am37x machines Chase Maupin
2010-07-29 12:26 ` [PATCH 2/2] x-load: add signGP to sourceipk Chase Maupin
2010-07-29 12:48 ` Koen Kooi
2010-07-29 15:11 ` John Willis
2010-07-29 17:41 ` Koen Kooi [this message]
2010-07-29 12:47 ` [PATCH 1/2] x-load_git: defined config for dm37x and am37x machines Koen Kooi
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='i2seh2$mrf$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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