Summary: | gpg-agent (1.9.20-r3) does not set environment variables | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Hyman <pete4abw> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | jakub |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gnupg.org | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Hyman
2006-05-26 06:19:49 UTC
try eval "$(/usr/bin/gpg-agent --daemon)" eval does just add the resulting flags to the environment :) Yes. that works. In the xml guide for gnupg, I `thought' the command used in the kde example was specific to kde. So I extracted the part in the () and tried it directly. BTW, what's with the gpg-experimental use flag? I did not realize gpg2 was not even being compiled until I tried to run it. It does not conflict with gpg, and IMHO, the flag is superfluous! Peter it was just in case a package went for gpg2 over gpg. Upstream still recommend gpg 1.4. It is a bit superfluous but it made people happy (I hope) bug 132343. (http://lists.gnupg.org/pipermail/gnupg-announce/2005q4/000209.html) oddly enough, this package is marked stable, and came through emerge as a slot og gnupg. I was a little confused by this! Since gpg2 is named differently, I do not see the potential for confusion. Although, perhaps consider adding an info notice in the ebuild about not having used gpg2-experimental. It's not apparent that gpg is not being compiled since the configure summary disappears quickly off the screen. JM2C |