Am 28.09.2016 um 19:48 schrieb Leo Famulari:
>> > Is this necessary for all python2 package variants? I rarely see this.
> For any use of the python2-variant system, yes. I replied to a lot of
> your submitted packages a couple days ago to point out that they needed
> this change.
I want to emphas
Am 28.09.2016 um 19:14 schrieb Leo Famulari:
> > + `(("python2-setuptools" ,python2-setuptools))
This will no longer be needed if my latest changes to the
python-build-systm will be accepted.
--
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implemen
On Wed, Sep 28, 2016 at 05:25:52PM +, ng0 wrote:
> Leo Famulari writes:
>
> > [ Unknown signature status ]
> > On Wed, Sep 28, 2016 at 05:02:56PM +, ng0 wrote:
> >> Subject: [PATCH] gnu: Add python-mailmanclient.
> >>
> >> * gnu/packages/mail.scm (python-mailmanclient): New variable.
> >
Leo Famulari writes:
> [ Unknown signature status ]
> On Wed, Sep 28, 2016 at 05:02:56PM +, ng0 wrote:
>> Subject: [PATCH] gnu: Add python-mailmanclient.
>>
>> * gnu/packages/mail.scm (python-mailmanclient): New variable.
>
>> +(define-public python2-mailmanclient
>> + (let ((base (package-
On Wed, Sep 28, 2016 at 05:02:56PM +, ng0 wrote:
> Subject: [PATCH] gnu: Add python-mailmanclient.
>
> * gnu/packages/mail.scm (python-mailmanclient): New variable.
> +(define-public python2-mailmanclient
> + (let ((base (package-with-python2
> + (strip-python2-variant python-m
ng0 writes:
> [ Unknown signature status ]
> A start for someone who wants to work on packaging mailman3, you need
> this and afterwards django-mailman3, then comes hyperkitty, and
> afterwards mailman3 itself I think.
> Added python2 variant because mailman3 has some mixture in the
> dependency
A start for someone who wants to work on packaging mailman3, you need
this and afterwards django-mailman3, then comes hyperkitty, and
afterwards mailman3 itself I think.
Added python2 variant because mailman3 has some mixture in the
dependency chain going on.
From bdcb5e7e77bd3e215016b3d9fde5094d6
