Difuse/packages
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
packages/lang/python/django/Makefile

52 lines
1.4 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 08:37:30 +00: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 06:29:46 +00: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 08:37:30 +00: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
python3-django: update to version 3.0.5 Signed-off-by: Peter Stadler <peter.stadler@student.uibk.ac.at>
2020-04-02 10:06:44 +00:00
PKG_VERSION:=3.0.5
django: bump to version 3.0.4 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2020-03-10 12:11:48 +00: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 08:37:30 +00: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 19:03:12 +00:00
PYPI_NAME:=Django
python3-django: update to version 3.0.5 Signed-off-by: Peter Stadler <peter.stadler@student.uibk.ac.at>
2020-04-02 10:06:44 +00:00
PKG_HASH:=d4666c2edefa38c5ede0ec1655424c56dc47ceb04b6d8d62a7eac09db89545c1
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 08:37:30 +00: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 08:52:49 +00: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 19:33:26 +00: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 19:03:12 +00: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 08:37:30 +00: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 12:25:39 +00:00
include ../python3-package.mk
django1: Add python3-django1 package This adds a Python 3 version of the django1 package. This also adds a python-django1-common package that contains a django-admin script based on the one in Debian[1]. This allows python-django1 and python3-django1 to be installed at the same time. python3-django conflicts with python-django1 (via python-django1-common) and python3-django1. This also updates older Python 3 Django plugin packages to depend on python3-django1, and newer plugin packages to depend on "django", which both python3-django and python3-django1 provide. Because of this dependency on either version of Django, the MDEPENDS for Python 3 Django plugin packages no longer functions correctly and has been removed. [1]: https://salsa.debian.org/python-team/modules/python-django/blob/debian/buster/debian/django-admin Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2020-02-05 11:13:45 +00:00
define Package/python3-django
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 12:25:39 +00:00
SUBMENU:=Python
SECTION:=lang
CATEGORY:=Languages
TITLE:=The web framework for perfectionists with deadlines.
URL:=https://www.djangoproject.com/
python3-asgiref: add package to fix django Django 3 has this package as dependency. Signed-off-by: Peter Stadler <peter.stadler@student.uibk.ac.at>
2020-01-28 20:31:58 +00:00
DEPENDS:= +python3 +python3-pytz +python3-sqlparse +python3-asgiref
django1: Add python3-django1 package This adds a Python 3 version of the django1 package. This also adds a python-django1-common package that contains a django-admin script based on the one in Debian[1]. This allows python-django1 and python3-django1 to be installed at the same time. python3-django conflicts with python-django1 (via python-django1-common) and python3-django1. This also updates older Python 3 Django plugin packages to depend on python3-django1, and newer plugin packages to depend on "django", which both python3-django and python3-django1 provide. Because of this dependency on either version of Django, the MDEPENDS for Python 3 Django plugin packages no longer functions correctly and has been removed. [1]: https://salsa.debian.org/python-team/modules/python-django/blob/debian/buster/debian/django-admin Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2020-02-05 11:13:45 +00:00
CONFLICTS:=python3-django1 python-django1-common
PROVIDES:=django
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 12:25:39 +00:00
VARIANT:=python3
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2016-04-30 08:37:30 +00: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 12:25:39 +00: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 06:29:46 +00: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 08:37:30 +00:00
endef
django: bump version to 2.2.7 and fix minor problems Add dependency on python3-sqlparse and use django-admin.py instead of django-admin as the latter depends on python3-pkg-resources. Signed-off-by: Peter Stadler <peter.stadler@student.uibk.ac.at>
2019-11-05 13:24:37 +00:00
define Py3Package/python3-django/install
$(INSTALL_DIR) $(1)/usr/bin
$(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/django-admin.py \
$(1)/usr/bin/django-admin
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 12:25:39 +00: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 06:29:46 +00:00
$(eval $(call BuildPackage,python3-django-src))
Reference in a new issue Copy permalink