Date: Mon, 02 Apr 2018 19:52:49 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 227149] Use the www/py-django meta port instead of the www/py-django18 port to move to Django 1.11 Message-ID: <bug-227149-21822-jyj0grugud@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227149-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-227149-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227149 Kai <freebsd_ports@k-worx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192021|0 |1 is obsolete| | --- Comment #8 from Kai <freebsd_ports@k-worx.org> --- Created attachment 192117 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D192117&action= =3Dedit Testcase with django variable in USE_PYTHON Hello everyone, thanks for all your input. Attached is another patch which implements Antoi= ne's and Kubilay's suggestions. A short overview about what the patch does: - create a new variable DJANGO_DEFAULT in Mk/bsd.default-versions.mk - add support for django for USE_PYTHON in Mk/Uses/python.mk - all ports, that depend on Django (except the meta port), are patched (deprecated ports have the value django:1.8 otherwise django is set either = to django:1.8+ or django:1.11+ This patch still lacks support for specific naming for django packages. The expected behavior for packages, that don't match the specific Django version, should be ignored. The patch needs of course thorough testing. Please consider this patch as a testcase and possible suggestion to develop= the idea further with it. It's not the definitive solution - for that the patch= is too far away to be perfect. -- Cheers Kai --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227149-21822-jyj0grugud>