From mboxrd@z Thu Jan 1 00:00:00 1970 From: "ng0" Subject: Re: postorius, v2 Date: Thu, 02 Feb 2017 12:13:42 +0000 Message-ID: <87wpd8zt6x.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> References: <87k29dqw8g.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <20170130112253.27338-1-contact.ng0@cryptolab.net> <58931D56.6010409@crazy-compilers.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZGFR-0003YQ-Nr for guix-devel@gnu.org; Thu, 02 Feb 2017 07:12:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZGFN-0007oW-L9 for guix-devel@gnu.org; Thu, 02 Feb 2017 07:12:21 -0500 Received: from latitanza.investici.org ([2001:888:2000:56::19]:30417) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cZGFN-0007mM-BV for guix-devel@gnu.org; Thu, 02 Feb 2017 07:12:17 -0500 In-reply-to: <58931D56.6010409@crazy-compilers.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Hartmut Goebel Cc: guix-devel Hartmut Goebel writes: > Hi, > > I just found that I did not verify the inputs carefully enough. Sorry. > Here are my comments: No problem. Thanks for checking again, I have no previous experience with django. > * 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+ Ok. > > 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? > > > 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. I'm waiting for further input on the django-XXX issue, then I will rebase and send updated patches. This will be important for the next step, hyperkitty, too. Thanks! -- ng0 . https://www.inventati.org/patternsinthechaos/