From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Split acme into both Python variants
Date: Thu, 31 Dec 2015 00:25:39 -0500 [thread overview]
Message-ID: <20151231052539.GA31978@jasmine> (raw)
In-Reply-To: <87bn98uein.fsf@gnu.org>
On Wed, Dec 30, 2015 at 04:45:04PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > 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.
>
> Sounds reasonable.
>
> > 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!
>
> What did you try exactly? The workaround is to explicitly list
> dependencies instead of using those computed by ‘package-with-python2’.
Despite trying the variations below, the build process kept failing as
described by Efraim in bug#22013 [0].
Here are the variations that I tested, based on reading python.scm:
(define-public python2-acme
(let ((acme (package-with-python2 python-acme)))
(package (inherit acme)
(propagated-inputs
`(("python2-cryptography" ,python2-cryptography)
,@(alist-delete "python-cryptography"
(package-propagated-inputs acme)))))))
(define-public python2-acme
(let ((acme (package-with-python2 python-acme)))
(package (inherit acme)
(propagated-inputs
`(("python2-pyopenssl" ,python2-pyopenssl)
("python2-cryptography" ,python2-cryptography)
,@(fold alist-delete (package-propagated-inputs acme)
'("python-pyopenssl" "python-cryptography")))))))
;; I don't understand this one
(define-public python2-acme
(let ((acme (package-with-python2 python-acme)))
(package (inherit acme)
(propagated-inputs
`(("python2-cryptography" ,python2-cryptography)
("python2-pyopenssl" ,python2-pyopenssl)
,@(alist-delete "python-pyopenssl"
(alist-delete "python-cryptography"
(package-propagated-inputs acme))))))))
[0]
http://lists.gnu.org/archive/html/bug-guix/2015-11/msg00124.html
>
> HTH,
> Ludo'.
prev parent reply other threads:[~2015-12-31 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 19:32 [PATCH 0/1] Split acme into both Python variants Leo Famulari
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 [this message]
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=20151231052539.GA31978@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.