From: "Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ipkg/opkg offical response
Date: Fri, 28 Mar 2008 17:17:45 +0100 [thread overview]
Message-ID: <47ED1A29.5090109@bolloretelecom.eu> (raw)
In-Reply-To: <200803272104.30232.openembedded@haerwu.biz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>
> So creation of "opkg-nogpg":
>
> require opkg_svn.bb EXTRA_OECONF += "--disable-gpg"
+1 for providing a gpg-less opkg
My main reason for not wanting gpg is not size (in my case gcrypt &
friends
get pulled into my image anyhow), it's that there is no indication of how
Packages.sig should be generated!
=> does package_ipk.bbclass need updating to generate Packages.sig?
- --
Jeremy LAINE
Bolloré telecom | 11bis, rue Scribe | F-75009 Paris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH7RopCL1n3lVB9EYRAkHkAKCrqjdCAdHw6QAZ72L3XzyATJN2hQCgw6uP
lotiZINAIi0I4mQr15gUxEs=
=8anQ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-03-28 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 17:17 ipkg/opkg offical response Richard Purdie
2008-03-27 19:25 ` Koen Kooi
2008-03-27 22:57 ` Jeremy Lainé
2008-03-27 23:09 ` Tom Rini
2008-03-28 0:30 ` Leon Woestenberg
2008-03-28 9:20 ` Richard Purdie
2008-03-28 9:43 ` Koen Kooi
2008-03-28 4:23 ` Marcin Juszkiewicz
2008-03-27 23:07 ` Richard Purdie
2008-03-28 7:03 ` kernel breackage, was " Koen Kooi
2008-03-28 9:17 ` Richard Purdie
2008-03-28 9:35 ` Koen Kooi
2008-03-27 20:04 ` Marcin Juszkiewicz
2008-03-28 0:15 ` Rod Whitby
2008-03-28 6:56 ` Koen Kooi
2008-03-28 9:27 ` Richard Purdie
2008-08-21 6:48 ` Mike (mwester)
2008-03-28 16:17 ` Jeremy Lainé [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=47ED1A29.5090109@bolloretelecom.eu \
--to=jeremy.laine@bolloretelecom.eu \
--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