From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 0/1] Split acme into both Python variants
Date: Mon, 21 Dec 2015 14:32:38 -0500 [thread overview]
Message-ID: <cover.1450726156.git.leo@famulari.name> (raw)
This patch splits the acme library into both Python variants. Currently,
its only user in Guix is the Python 2 official Let's Encrypt client, but
there is other software out there that supports Python 3.
I tried and tried to make the python2-acme version inherit more from
python-acme but this is what I got working.
I did try to apply the solution used in python2-pyopenssl and
python2-oauthlib [0] but I couldn't make it work. I think the issue is
that python2-acme uses both python2-pyopenssl and python2-cryptography,
so there are multiple layers of translation to watch out for.
Suggestions welcome!
I think we should keep these in the same module as letsencrypt, because
it will make it easier to remember to update them together, which
appears to be necessary.
[0]
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22013
Leo Famulari (1):
gnu: Split acme into python-acme and python2-acme.
gnu/packages/tls.scm | 82 +++++++++++++++++++++++++++++++---------------------
1 file changed, 49 insertions(+), 33 deletions(-)
--
2.6.2
next reply other threads:[~2015-12-21 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 19:32 Leo Famulari [this message]
2015-12-21 19:32 ` [PATCH 1/1] gnu: Split acme into python-acme and python2-acme Leo Famulari
2015-12-30 15:45 ` [PATCH 0/1] Split acme into both Python variants Ludovic Courtès
2015-12-31 5:25 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1450726156.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).