unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: postorius, v2
Date: Sun, 5 Feb 2017 01:28:01 +0000	[thread overview]
Message-ID: <20170205012801.mqsr5cpfxkrwjbqd@wasp> (raw)
In-Reply-To: <878tpomgea.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>

On 17-02-02 21:28:29, ng0 wrote:
> 
> Hartmut Goebel writes:
> 
> > Hi,
> >
> > I just found that I did not verify the inputs carefully enough. Sorry.
> > Here are my comments:
> >
> >   * python-defusedxml: okay
> >   * python-openid: okay
> >   * python-django-allauth:
> >       o openid, request-oauthlib requests ought to be propagated inputs
> >       o mock is native, okay, but only required for the python2 variant
> >       o Why is django a native input? See below for discussion
> >   * python-django-gravatar2, may be okay, see below for discussion.
> >   *  python-django-mailman3
> >       o All "inputs" except django need to be propagated inputs.
> >       o Regarding django: see below
> >   * * postorius: okay (this is an application, so no propagated inputs
> >     are required)
> >
> >
> > And as we just learned about the licenses: python-django-mailman3 should
> > be gpl3+
> >
> >
> > I'm unsure about the correct handling of django in django-XXX. Can we
> > find rules for this to make future packager's life easier?
> >
> > Should django be a "normal" input or a "native" one? What does this
> > depend on?
> >
> 
> For now I will go with (input) and not (native-input). If that's
> not okay, we can still fix it afterwards?
> I will send the new patchseries tomorrow.
> 
> Thanks!

I will send the rebased series tomorrow afternoon. I will not be in the
position to answer very much next week, so if no one else replies to the
django issue, you could decide on what's the best approach practically.
Changes to individual packages can still be applied afterwards.

> > Clear is: django-XXX should not "propagate" django:
> >
> >   * django is a framework, django-XXX is an extension for this framework.
> >   * If some application is using django-XXX, I'd expect it to have
> >     django specified as "input", too, since primary it is a django
> >     application. Maybe even djangoXXX is an optional component
> >
> >
> > Just for the records:
> >
> >   * django-XXX should propagate other django extension it requires.
> >       o If some application is using django-XXX, if should not care
> >         about other django extensions django-XXX requires. This is the
> >         same like as it does not have to care about other python
> >         packages django-XXX requires.
> 
> 
> -- 
> ng0 . https://www.inventati.org/patternsinthechaos/
> 

-- 
ng0 -- https://www.inventati.org/patternsinthechaos/

      reply	other threads:[~2017-02-05  1:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 23:26 Mailman3 frontend number one: postorius contact.ng0
2017-01-29 23:26 ` [PATCH 1/6] gnu: Add python-defusedxml contact.ng0
2017-01-29 23:26 ` [PATCH 2/6] gnu: Add python-openid contact.ng0
2017-01-29 23:26 ` [PATCH 3/6] gnu: Add python-django-allauth contact.ng0
2017-01-29 23:26 ` [PATCH 4/6] gnu: Add python-django-gravatar2 contact.ng0
2017-01-29 23:26 ` [PATCH 5/6] gnu: Add python-django-mailman3 contact.ng0
2017-01-29 23:26 ` [PATCH 6/6] gnu: Add postorius contact.ng0
2017-01-30  8:48   ` Hartmut Goebel
2017-01-30  9:10     ` ng0
2017-01-30  9:20       ` Hartmut Goebel
2017-01-30 10:12         ` ng0
2017-01-29 23:31 ` Mailman3 frontend number one: postorius ng0
2017-01-30 11:22   ` postorius, v2 contact.ng0
2017-01-30 11:22     ` [PATCH 1/6] gnu: Add python-defusedxml contact.ng0
2017-01-30 11:22     ` [PATCH 2/6] gnu: Add python-openid contact.ng0
2017-01-30 11:22     ` [PATCH 3/6] gnu: Add python-django-allauth contact.ng0
2017-01-30 11:22     ` [PATCH 4/6] gnu: Add python-django-gravatar2 contact.ng0
2017-01-30 11:22     ` [PATCH 5/6] gnu: Add python-django-mailman3 contact.ng0
2017-01-30 11:22     ` [PATCH 6/6] gnu: Add postorius contact.ng0
2017-01-31 13:40     ` postorius, v2 Hartmut Goebel
2017-02-02 11:51     ` Hartmut Goebel
2017-02-02 12:13       ` ng0
2017-02-02 12:28       ` Python packaging rules again (was: postorius, v2) Hartmut Goebel
2017-02-02 21:28       ` postorius, v2 ng0
2017-02-05  1:28         ` ng0 [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

  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=20170205012801.mqsr5cpfxkrwjbqd@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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).