From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] opkg: Add option to enable package verification support with GnuPG
Date: Thu, 28 Feb 2013 15:38:19 +0100 [thread overview]
Message-ID: <20130228153819.57a2c5ae@skate> (raw)
In-Reply-To: <64891469.UzFDExKfyb@arawn>
Dear Philipp Claves,
On Thu, 28 Feb 2013 15:04:42 +0100, Philipp Claves wrote:
> This set of patches enables the opkg support for verifying package signatures
> with gnupg.
>
> The first two patches add the required libraries (libassuan and libgpgme).
> The third adds new option: opkg-gnupg-support. It selects the needed packages
> and sets the --enable-gpg configure option for opkg.
>
> The patch dependency chain is:
> (0003) opkg -> (0002) libgpgme -> (0001) libassuan
>
> Comments are welcome.
Thanks, they look (almost) good! Could you submit them, one mail per
patch, preferably using git send-email?
On libassuan, please wrap the help text, and add a final newline at the
end of the .mk file.
On libgpgme, please wrap the help text, add the final newline at the
end of the .mk file. The --with-gpg=/usr/bin/gpg doesn't look very
good. gpg is not a mandatory dependency of Buildroot, so if libgpgme
really needs gpg, then we should build host-gnupg I guess. But does it
really need it? Can you detail this --with-gpg option? Or maybe it's
just the path where gpg will be installed on the target? If it's the
case, then maybe a comment would be appropriate to clarify this.
In the opkg patch, in the .mk file, you should use
BR2_PACKAGE_OPKG_GPG_SIGN in your condition rather than
BR2_PACKAGE_LIBGPGME. Also, in your Config.in, you add GNUPG as a
dependency, but it is not listed in the .mk file. This is sometimes
correct if it is only a runtime dependency, in which case we usually
put a comment in the Config.in just above the corresponding select line.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-28 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 14:04 [Buildroot] [PATCH] opkg: Add option to enable package verification support with GnuPG Philipp Claves
2013-02-28 14:38 ` Thomas Petazzoni [this message]
[not found] ` <2380880.Y2Uig4QfWB@arawn>
2013-03-01 10:18 ` Thomas Petazzoni
2013-03-01 13:38 ` [Buildroot] [PATCH 1/3] Add libassuan IPC library Philipp Claves
2013-03-01 13:38 ` [Buildroot] [PATCH 2/3] Add GnuPG Made Easy (gpgme) library Philipp Claves
2013-03-01 13:38 ` [Buildroot] [PATCH 3/3] opkg: Add gnupg signature checking support Philipp Claves
2013-04-08 10:26 ` Philipp Claves
2013-04-09 16:03 ` Arnout Vandecappelle
2013-04-10 17:40 ` Thomas Petazzoni
2013-04-26 11:41 ` Philipp Claves
2013-07-31 16:14 ` [Buildroot] [PATCH 1/3] Add libassuan IPC library Thomas Petazzoni
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=20130228153819.57a2c5ae@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.