non port: www/py-django-babel/Makefile |
Number of commits found: 12 |
Thursday, 30 Jun 2022
|
19:51 Rene Ladan (rene)
cleanup: Remove expired ports:
2022-06-30 www/py-django-common-helpers: No longer maintained, doesn't work with
newer versions of Django
2022-06-30 www/py-django: Was used as a metaport, no longer required
2022-06-30 www/py-django-sudo: Abandoned upstream, not compatible with newer
versions of Django
2022-06-30 www/py-django-bootstrap-form: No longer maintained, not compatible
with newer versions of Django
2022-06-30 www/py-django-babel: Upstream no longer maintained, please use
www/py-enmerkar instead
2022-06-30 www/py-django-bulk-update: No longer maintained, not compatible with
newer versions of Django
2022-06-30 www/py-django-happenings-update: Upstream no longer maintained, not
compatible with newer versions of Django
2022-06-30 www/py-django-compat: No longer maintained, doesn't work with newer
versions of Django
2022-06-30 www/py-django-modern-rpc: Not compatible with newer versions of
Django
ff89f3f |
Friday, 21 Jan 2022
|
19:00 Kai Knoblich (kai)
www/py-django-babel: Deprecate and set to expire
There hasn't been an update since 2019 and the compatibility with newer
versions of Django isn't present. As an alternative, www/py-enmerkar
can be used, which is a fork of it.
a78e628 |
Tuesday, 6 Apr 2021
|
14:31 Mathieu Arnold (mat)
Remove # $FreeBSD$ from Makefiles.
305f148 |
Thursday, 14 Jan 2021
|
14:34 dbaio
Remove PY_SPHINX from ports using Python 3
Approved by: portmgr blanket
Differential Revision: https://reviews.freebsd.org/D28093
|
Saturday, 12 Sep 2020
|
12:55 zi
- Reset MAINTAINER due to multiple fatal bounces
Reported by: portscout!
|
Monday, 11 May 2020
|
23:51 dbaio
Update Sphinx
- Repocopy textproc/py-sphinx to textproc/py-sphinx18
Update it to 1.8.5 (latest version from 1.8.X).
This version supports Python 2 and 3.
Add test target.
- textproc/py-sphinx: Update to 3.0.2
Python 3 only (3.5+).
Add test target.
- Mk/Uses/python.mk: Add PY_SPHINX
Shared macro to use with flavors and not break
ports with USES=python (all versions).
Python >=3.5 --> textproc/py-sphinx (v3.0.2)
Python < 3.5 --> textproc/py-sphinx18 (v1.8.5)
All ports that uses sphinx were changed to use the new variable
${PY_SPHINX} in the dependency line, exceptions:
* Ports that fails to build with sphinx 3.0.2 because of code.
They are pointing to textproc/py-sphinx18 directly.
There aren't many ports.
* Ports that doesn't know Python flavors.
- Add several patches to fix Sphinx consumers
The most common issues are related with pkg-plist, the output
files from Sphinx changes between versions, keep this dynamically
is the better approach.
This will save time in future sphinx updates.
PR: 245629
Exp-run by: antoine
|
Wednesday, 22 Apr 2020
|
14:44 kai
www/py-horizon: Update to 17.1.0
* Also assign the port to Django 2.2 because Django 1.11 is End-of-Life
since April.
* Do the same for its dependencies and bump PORTREVISION accordingly.
* Add an option to let users choose between the supported caching backends.
Although databases/py-python-memcached isn't listed in requirements.txt
it's used as default caching backend and needed at runtime.
PR: 245432
Approved by: maintainer timeout (14 days)
|
Monday, 9 Jul 2018
|
19:21 miwi
- Update to 0.6.2
PR: 228850
Submitted by: freebsd_ports@k-worx.org
Approved by: maintainer
Sponsored by: iXsystems Inc.
|
Wednesday, 20 Jun 2018
|
17:05 mat
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
|
Thursday, 30 Nov 2017
|
15:50 mat
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
|
Friday, 14 Apr 2017
|
09:02 amdmi3
- Fix LICENSE
- Add LICENSE_FILE
|
Monday, 12 Dec 2016
|
16:05 novel
Add py-django-babel 0.5.1, utilities for using Babel in django.
PR: 215149
Submitted by: Alexander Nusov <alexander.nusov@nfvexpress.com>
|
Number of commits found: 12 |