From owner-freebsd-ports@freebsd.org Thu Mar 7 06:55:11 2019 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C387151D798 for ; Thu, 7 Mar 2019 06:55:11 +0000 (UTC) (envelope-from leres@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9F426C825 for ; Thu, 7 Mar 2019 06:55:10 +0000 (UTC) (envelope-from leres@freebsd.org) Received: from ice.alameda.xse.com (unknown [IPv6:2001:558:6045:10:9084:9e0:4b6d:eb99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: leres) by smtp.freebsd.org (Postfix) with ESMTPSA id 5A899A789 for ; Thu, 7 Mar 2019 06:55:10 +0000 (UTC) (envelope-from leres@freebsd.org) From: Craig Leres Subject: Django versions To: freebsd-ports@freebsd.org Message-ID: Date: Wed, 6 Mar 2019 22:55:08 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: A9F426C825 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Mar 2019 06:55:11 -0000 I'm working on a port for mailman 3. I want to use django 2.1 because that's what I'm using on the systems I'm currently running mailman 2 on you can't really run different version of django on the same system). But it turns out a lot of ports have RUN_DEPENDS for www/py-django111. One possible solution would be to change these dependencies to the www/py-django meta port. This allows the user pick the version of django via py-django options. But I see a bunch of ports got added last month: www/py-dj21-django-cors-headers www/py-dj21-django-debug-toolbar www/py-dj21-django-filter www/py-dj21-django-js-asset www/py-dj21-django-mptt www/py-dj21-django-tables2 www/py-dj21-django-taggit www/py-dj21-django-taggit-serializer www/py-dj21-django-timezone-field www/py-dj21-djangorestframework www/py-dj21-drf-yasg which are the py-django21 version of the py-django111 ports with similar names. Anyway the current situation prevents folks from using py-django20 if that's what they want. And a ton of changes will be needed when django22 (currently in beta) arrives. The downside I see to changing dependencies from py-django111 to py-django is that only the py-django111 versions of things were get built/tested automatically (due to py-django111 being the default version). And I think there are issues for ports that don't work with all version of django (is there a way for a port's Makefile to know what version of django got installed?) Are there other problems? Are there other solutions? Flavors comes to mind but I'm told "doubly flavored" ports (python flavor vs. django flavor) are very difficult. Without any changes I'll need to add DJANGO111 and DJANGO21 to my mailman 3 port and forget about folks being able to use django20. This will be extra messy because mailman 3 is split across several different packages. Craig