From: Paul Barker <paul@paulbarker.me.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: Gnupg recipe fixes
Date: Mon, 25 Mar 2013 12:57:28 +0000 [thread overview]
Message-ID: <20130325125728.00004c11@unknown> (raw)
In-Reply-To: <1364172907-14541-1-git-send-email-paul@paulbarker.me.uk>
On Mon, 25 Mar 2013 00:55:05 +0000
Paul Barker <paul@paulbarker.me.uk> wrote:
> I'm setting up a signed apt repository of .deb packages built using
> OpenEmbedded and I've ran into an issue with apt-get on the target
> board not being able to find 'gpgv' to verify the signatures. This is
> installed as 'gpgv2' in the gnupg recipe. Therefore I've used
> update-alternatives to create the appropriate link.
>
I've re-thought this already. Is update-alternatives the right thing to
use here? Maybe not as there isn't anything else that provides gpgv and
gnupg_1.* and gnupg_2.* probably can't co-exist on the same install. I
could just add a line to do_install_append() to create the gpgv link
manually, similar to how the link for gpg is already created. Please
let me know which is the better solution here.
I also noticed that gnupg_1.4.7.bb splits gpgv into a separate package
but gnupg_2.0.19 doesn't. I could write a patch to modify one of these
to match the other if desired?
Thanks,
--
Paul Barker
Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk
next prev parent reply other threads:[~2013-03-25 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 0:55 Gnupg recipe fixes Paul Barker
2013-03-25 0:55 ` [PATCH 1/2] gnupg: Replace manual link with update-alternatives Paul Barker
2013-03-25 0:55 ` [PATCH 2/2] gnupg: Added update-alternatives entry for gpgv Paul Barker
2013-03-25 12:57 ` Paul Barker [this message]
2013-03-25 13:25 ` Gnupg recipe fixes Richard Purdie
2013-03-25 13:32 ` Paul Barker
2013-03-25 13:39 ` Richard Purdie
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=20130325125728.00004c11@unknown \
--to=paul@paulbarker.me.uk \
--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