[Bug 227149] Use the www/py-django meta port instead of the www/py-django18 port to move to Django 1.11
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Apr 1 10:43:10 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227149
--- Comment #6 from Kai <freebsd_ports at k-worx.org> ---
Thank you for the references to the review and PRs. If I understand this right
by the given facts/suggestions then the desired approach would be like:
- create a new variable, e.g. DJANGO_DEFAULT in bsd.default-versions.mk
- create a new variable, e.g. django:X.XX[+] for USE_PYTHON in Uses/python.mk
For the next examples I'll refer to following django ports:
- www/py-django-filer (depends also on graphics/py-django-easy-thumbnails
- graphics/py-django-easy-thumbnails
Let's assume that the new variables above mentioned are implemented into the
ports framework, then the sections for RUN_DEPENDS and USE_PYTHON should be
changed to:
For www/py-django-filer:
> RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}django-easy-thumbnails>=0:graphics/py-django-easy-thumbnails@${FLAVOR} \
> ${PYTHON_PKGNAMEPREFIX}pillow>=0:graphics/py-pillow@${FLAVOR}
> USE_PYTHON= autoplist distutils django
For graphics/py-django-easy-thumbnails (the RUN_DEPENDS can be removed):
> USE_PYTHON= distutils autoplist django
A bulk run for both py27 and py36 flavors with a Django default version of 1.11
will produce following Django v1.11 packages:
- py27-django-filer
- py27-django-easy-thumbnails
- py36-django-filer
- py36-django-easy-thumbnails
If I understood the extent to that point correctly, then the following example
should fail with DJANGO_VERSION set to 1.11 (as intended):
For port graphics/py-django-easy-thumbnails change USE_PYTHON to:
> USE_PYTHON= distutils autoplist django1.8
This should produce a build error for both py27 and py36 flavors if I'm
correct?
To resolve that issue, one can change USE_PYTHON to:
> USE_PYTHON= distutils autoplist django1.8+
Then the build of both Python flavors should work again.
--
Cheers
Kai
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-python
mailing list