mirror
/
openwrt-packages
mirror of https://git.openwrt.org/feed/packages.git
1
0
Fork 0
Code Releases Activity
openwrt-packages/lang/python/django/Makefile

51 lines
1.2 KiB
Makefile
Raw Normal View History

seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
#
django: split django1 package and update to 2.2.6 After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-10-11 08:29:46 +02:00
# Copyright (C) Alexandru Ardelean <ardeleanalex@gmail.com>
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
include $(TOPDIR)/rules.mk
PKG_NAME:=django
django: split django1 package and update to 2.2.6 After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-10-11 08:29:46 +02:00
PKG_VERSION:=2.2.6
django: Update to 1.11.24 Fixes a whole bunchs of CVEs: CVE-2019-3498 CVE-2019-6975 CVE-2019-12308 CVE-2019-12781 CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235 Signed-off-by: Rosen Penev <rosenp@gmail.com>
2019-09-18 23:40:47 +02:00
PKG_RELEASE:=1
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
treewide: Use pypi.mk for Python packages This updates all Python packages that download their source from PyPi to use pypi.mk. This will allow future improvements/changes to pypi.mk to affect all relevant packages. This also makes it easier for future Python packages to start using pypi.mk, when it's clear how it is used in existing packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2019-10-20 21:03:12 +02:00
PYPI_NAME:=Django
django: split django1 package and update to 2.2.6 After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-10-11 08:29:46 +02:00
PKG_HASH:=a8ca1033acac9f33995eb2209a6bf18a4681c3e5269a878e9a7e0b7384ed1ca3
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
treewide,python: take over maintainership from Gergely Kiss This change changes the maintainer to `Alexandru Ardelean <ardeleanalex@gmail.com` for all Python packages owned by `Gergely Kiss <mail.gery@gmail.com>` No functional changes. Bumping PKG_RELEASE on each package that is updated. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-03-14 09:52:49 +01:00
PKG_MAINTAINER:=Alexandru Ardelean <ardeleanalex@gmail.com>
django: Update to 1.11.17 Added PKG_CPE_ID for proper CVE tracking. Some Makefile rearrangements for consistency. Signed-off-by: Rosen Penev <rosenp@gmail.com>
2018-12-16 20:33:26 +01:00
PKG_LICENSE:=BSD-3-Clause
PKG_LICENSE_FILES:=LICENSE LICENSE.python
PKG_CPE_ID:=cpe:/a:djangoproject:django
treewide: Use pypi.mk for Python packages This updates all Python packages that download their source from PyPi to use pypi.mk. This will allow future improvements/changes to pypi.mk to affect all relevant packages. This also makes it easier for future Python packages to start using pypi.mk, when it's clear how it is used in existing packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2019-10-20 21:03:12 +02:00
include ../pypi.mk
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
include $(INCLUDE_DIR)/package.mk
django: convert to python pkg format + add python3 variant This also updates all dependencies to use the new `python-django` package. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-03 14:25:39 +02:00
include ../python3-package.mk
define Package/django/Default
SUBMENU:=Python
SECTION:=lang
CATEGORY:=Languages
TITLE:=The web framework for perfectionists with deadlines.
URL:=https://www.djangoproject.com/
django: move django* packages under django submenu This changes the python[3]-django dependencies in packages to be non-selecting, and adds an MDEPENDS line so that the *-src packages get placed inside the django menu as well. Added MENU:= to the src-package definitions in python[3]-package.mk, so it does not import that setting from the binary package. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
2019-07-09 14:12:06 +02:00
MENU:=1
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
endef
django: convert to python pkg format + add python3 variant This also updates all dependencies to use the new `python-django` package. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-03 14:25:39 +02:00
define Package/python3-django
$(call Package/django/Default)
DEPENDS:= \
+PACKAGE_python3-django:python3 \
+PACKAGE_python3-django:python3-pytz
VARIANT:=python3
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
endef
django: convert to python pkg format + add python3 variant This also updates all dependencies to use the new `python-django` package. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-03 14:25:39 +02:00
define Package/python3-django/description
django: split django1 package and update to 2.2.6 After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-10-11 08:29:46 +02:00
The web framework for perfectionists with deadlines (LTS 2.2 series).
Python3 only.
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 10:37:30 +02:00
endef
django: convert to python pkg format + add python3 variant This also updates all dependencies to use the new `python-django` package. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-03 14:25:39 +02:00
$(eval $(call Py3Package,python3-django))
$(eval $(call BuildPackage,python3-django))
django: split django1 package and update to 2.2.6 After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-10-11 08:29:46 +02:00
$(eval $(call BuildPackage,python3-django-src))