From owner-freebsd-ports@freebsd.org Thu Mar 7 07:22:56 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 D1C0315202BA for ; Thu, 7 Mar 2019 07:22:55 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB8696DA66; Thu, 7 Mar 2019 07:22:54 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: by mail-ed1-f45.google.com with SMTP id f19so12527532eds.12; Wed, 06 Mar 2019 23:22:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jCQn808AxSGWTRVG46GDR3A37MT9Kzjq0m7JnvlpF/Q=; b=IhNnqA02HvqwEXlNgW4rNLWh1KSeY8rZFDZW7P2D5+T94NdievHAWYbw7KfDYk95S0 6PrCHXXA1Z84uLz9jG/yD7nPSLrfXeUnuuDCvfY+Pw4nm+58U7/QPTTL5f/TtLromNne mzEiBUdXZVJkeB317qaWW3XfQuwZ5+Vc9nwx/830Lh0gPLHdqb3NB7Pj4DZTUOWORnax 46/iaxOCyjJxTf3ZjmowkgMI2eGauF/MkXjoCqNfdQHuQMgh9EfxZX+3ZxS2x2mapfbl se/QMQY45BQ6JSnIiixxMeH6P0c/woqkZ1n0XuhVuEHKhO9HqCv+VI6V0tVIaY18AKZQ PvoA== X-Gm-Message-State: APjAAAV2MkgMsdLENZrG3RawXVISy/5DWjfexQzuU48lbiUUIS3ghHs/ NCUQRIwMFbTyRzV53GoqMMyqpx1txRyfZAZLm9CqT9GB X-Google-Smtp-Source: APXvYqwjH1TvXFbi6MRgvrBGjDO4zKxQ0cpfYx73IxUh4MFJ4G4F352e9KPc1c8rCr5443jDwGbTQdJAsu4xoLp9/Zs= X-Received: by 2002:a17:906:37c2:: with SMTP id o2mr6827028ejc.127.1551943367725; Wed, 06 Mar 2019 23:22:47 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Antoine Brodin Date: Thu, 7 Mar 2019 08:22:36 +0100 Message-ID: Subject: Re: Django versions To: Craig Leres Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: EB8696DA66 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of antoinebrodinfreebsd@gmail.com designates 209.85.208.45 as permitted sender) smtp.mailfrom=antoinebrodinfreebsd@gmail.com X-Spamd-Result: default: False [-4.80 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[45.208.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; IP_SCORE(-1.80)[ip: (-3.05), ipnet: 209.85.128.0/17(-3.84), asn: 15169(-2.04), country: US(-0.07)]; FORGED_SENDER(0.30)[antoine@freebsd.org,antoinebrodinfreebsd@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[antoine@freebsd.org,antoinebrodinfreebsd@gmail.com]; RCVD_COUNT_TWO(0.00)[2] 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 07:22:56 -0000 On Thu, Mar 7, 2019 at 8:14 AM Craig Leres wrote: > > 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. Hi, Please don't use the django metaport, this port should be removed and people should stop using hacks. Someone needs to integrate a USE_PYTHON=django in python.mk Antoine