From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hartmut Goebel Subject: Python packaging rules again (was: postorius, v2) Date: Thu, 2 Feb 2017 13:28:14 +0100 Message-ID: <589325DE.9020802@crazy-compilers.com> 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; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZGUx-0000yN-HR for guix-devel@gnu.org; Thu, 02 Feb 2017 07:28:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZGUu-0000cn-8X for guix-devel@gnu.org; Thu, 02 Feb 2017 07:28:23 -0500 Received: from mail-out.m-online.net ([212.18.0.9]:50962) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cZGUu-0000bw-1h for guix-devel@gnu.org; Thu, 02 Feb 2017 07:28:20 -0500 Received: from frontend01.mail.m-online.net (unknown [192.168.8.182]) by mail-out.m-online.net (Postfix) with ESMTP id 3vDfRQ1j7zz3hjlC for ; Thu, 2 Feb 2017 13:28:18 +0100 (CET) Received: from localhost (dynscan1.mnet-online.de [192.168.6.68]) by mail.m-online.net (Postfix) with ESMTP id 3vDfRP3r3czvkWJ for ; Thu, 2 Feb 2017 13:28:17 +0100 (CET) Received: from mail.mnet-online.de ([192.168.8.182]) by localhost (dynscan1.mail.m-online.net [192.168.6.68]) (amavisd-new, port 10024) with ESMTP id uBvD_HybGSii for ; Thu, 2 Feb 2017 13:28:15 +0100 (CET) Received: from hermia.goebel-consult.de (ppp-93-104-65-145.dynamic.mnet-online.de [93.104.65.145]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS for ; Thu, 2 Feb 2017 13:28:15 +0100 (CET) Received: from [192.168.110.2] (lenashee.goebel-consult.de [192.168.110.2]) by hermia.goebel-consult.de (Postfix) with ESMTP id 81AFE60621 for ; Thu, 2 Feb 2017 13:28:14 +0100 (CET) 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: guix-devel Hi, I'm reposting this with a different subject, since this question is not only related to postorius: What do others think about the central question: Should django be a "normal" input or a "native" one? What does this depend on? What are the rules for? > 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. -- Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |