It would be nice to have the Debian package signing-party available as an ebuild as well. It contains tools to print fingerprints, download keys, send out signatures, etc. See the URL for details. The tools are written in perl, and the deps are already available as Gentoo ebuilds. It should be possible to get those scripts functional on almost all architectures. I am not sure if the package should be named signing-party, after the debian package, or instead pgp-tools, after the project name. My ebuild is independent from this issue, by containing the name of the debian package in MY_PN.
Created attachment 78801 [details] app-crypt/signing-party/signing-party-0.4.4.2.ebuild (v.1) My ebuild, instaling pgp-tools from the sources contained in the debian-package signing-party_0.4.4_2. I tried to make the naming as robust as possible, so that new versions should be possible easily. An alternative it would be possible to fetch sources directly from svn. But I've not used subversion.eclass so far, and I'm not sure if this would make sense, as it would introduce an unneeded dep on subversion.
- it's doc/${PF}, not doc/${P} - src_compile() is superfluous
*** Bug 132664 has been marked as a duplicate of this bug. ***
Attached is a new ebuild for version 0.4.6 I wrote before I found the 0.4.4.2 ebuild, so it takes a slightly different, more simple approach: - Applying the patches from debian is not necessary because they contain, at least all patches I looked at on http://ftp.debian.org/debian/pool/main/s/signing-party/, only changes to the debian/ directory, which is only of interest to debian packaging and not to ebuild. This simplifies src_unpack() a bit. - No unneccessary src_compile() - A different approach to src_install(): Do not use debian/install. I also didn't install gpgsigs-lt2k5*.txt as documentation, since it isn't. Also a question: Where did you get v0.4.4.2? As far as I can see, there is/was no version 0.4.4, only 0.3.0 and then 0.4.5.
Created attachment 86418 [details] signing-party-0.4.6.ebuild
Created attachment 86419 [details] signing-party-0.4.6.ebuild (double-post, sorry)
(In reply to comment #4) > - A different approach to src_install(): Do not use debian/install. I would still suggest to mention debian/install in some comment at least, so that when some new version introduces a new tool, the one doing the gentoo version bump would notice the change more easily. > Also a question: Where did you get v0.4.4.2? As far as I can see, there is/was > no version 0.4.4, only 0.3.0 and then 0.4.5. Well, the sources for were there where my ebuild got them from. They are no longer, I don't know why. Talking of sources: I suggest you use the mirror:// pseudo protocol in SRC_URI, so that the configured debian mirrors are used: SRC_URI="mirror://debian/pool/main/s/signing-party/signing-party_${PV}.orig.tar.gz"
Created attachment 86421 [details] signing-party-0.4.6.ebuild (v1)
(In reply to comment #7) > (In reply to comment #4) > > - A different approach to src_install(): Do not use debian/install. > > I would still suggest to mention debian/install in some comment at least, so > that when some new version introduces a new tool, the one doing the gentoo > version bump would notice the change more easily. Good idea, I added a comment to the start of src_install() > > Also a question: Where did you get v0.4.4.2? As far as I can see, there is/was > > no version 0.4.4, only 0.3.0 and then 0.4.5. > > Well, the sources for were there where my ebuild got them from. They are no > longer, I don't know why. Talking of sources: I suggest you use the mirror:// > pseudo protocol in SRC_URI, so that the configured debian mirrors are used: > SRC_URI="mirror://debian/pool/main/s/signing-party/signing-party_${PV}.orig.tar.gz" Sure, changed SRC_URI to use mirror.
Mail signature for [userid] to '[email address]'? [Y/n] No data from gpg for list-key [long keyid] Exiting subroutine via next at /usr/bin/caff line 778. Obviously the key will not be mailed.
Imported to CVS with small changes, thanks for providing an ebuild ;) In reply to comment #10: Which version of gnupg do you use?
Please try it and reopen if the bug still persists
