Date: Sun, 01 Apr 2018 09:10:13 +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-v1UF2M1umM@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227149 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[PATCH] Use the |Use the www/py-django meta |www/py-django meta port |port instead of the |instead of the |www/py-django18 port to |www/py-django18 port to |move to Django 1.11 |move to Django 1.11 | Status|New |Open --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- -1 on this too. It feels odd switching to less explicit django version for each ports dependency, via a meta port who's versions will change over time. This is especially the case given some complex interdependent version dependencies for many django ports (and future ones), particularly over time as version compatibility changes. Essentially, only a single installed version of django can be supported at any one time in a single python version system site-packages location, the proper solution to which is DEFAULT_VERSIONS support (See: bug 222724's review, leaving aside implementation specifics/design choices). That said, if the metaport ONLY implemented (and depended on) the users selected (or the default) DEFAULT_VERSION of django, that might be nice, if its possible. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227149-21822-v1UF2M1umM>