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

69 lines
1.6 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
#
seafile: update to version 6.0.7 Update several dependencies, as well: * django-compressor -> 2.1.1 * django-constance -> 1.3.4 * django-restframework -> 3.5.4 * django-statici18n -> 1.3.0 * django -> 1.8.17 * openpyxl -> 2.4.2 * python-dateutil -> 2.6.0 * python-urllib3 -> 1.20 Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
2017-02-13 22:03:14 +01:00
# Copyright (C) 2007-2017 OpenWrt.org
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-restframework
django-restframework: Update to 3.9.0 Signed-off-by: Rosen Penev <rosenp@gmail.com>
2018-10-22 23:44:03 +02:00
PKG_VERSION:=3.9.0
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_RELEASE:=5
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:=djangorestframework
django-restframework: Update to 3.9.0 Signed-off-by: Rosen Penev <rosenp@gmail.com>
2018-10-22 23:44:03 +02:00
PKG_HASH:=607865b0bb1598b153793892101d881466bd5a991de12bd6229abb18b1c86136
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +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-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
PKG_LICENSE:=BSD-3-Clause
PKG_LICENSE_FILES:=LICENSE.md
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
treewide: use local python-package.mk & python3-package.mk files This guarantees for the package feeds that the mk files will always be available for all packages. Will need to see about external-feed Python packages a bit later. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2018-01-10 08:56:52 +01:00
include ../python-package.mk
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
include ../python3-package.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
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
define Package/$(PKG_NAME)/Default
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
SUBMENU:=Python
SECTION:=lang
CATEGORY:=Languages
TITLE:=Web APIs for Django, made easy.
django-restframework: update to 3.8.2 Some minor Makefile adjustments including standard python URL. Signed-off-by: Rosen Penev <rosenp@gmail.com>
2018-09-17 23:36:21 +02:00
URL:=https://www.django-rest-framework.org
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-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
define Package/python-$(PKG_NAME)
$(call Package/$(PKG_NAME)/Default)
DEPENDS:= \
+PACKAGE_python-$(PKG_NAME):python \
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
python-django1
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
VARIANT:=python
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
MDEPENDS:=python-django1
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
endef
define Package/python-$(PKG_NAME)/description
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
Web APIs for Django, made easy.
endef
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
define Package/python3-$(PKG_NAME)
$(call Package/$(PKG_NAME)/Default)
DEPENDS:= \
+PACKAGE_python3-$(PKG_NAME):python3 \
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
python3-django
django-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
VARIANT:=python3
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
MDEPENDS:=python3-django
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-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
define Package/python3-$(PKG_NAME)/description
$(call define Package/python-$(PKG_NAME)/description)
.
(Variant for 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-restframework: update packaging format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2019-06-25 09:17:10 +02:00
$(eval $(call PyPackage,python-$(PKG_NAME)))
$(eval $(call BuildPackage,python-$(PKG_NAME)))
$(eval $(call BuildPackage,python-$(PKG_NAME)-src))
$(eval $(call Py3Package,python3-$(PKG_NAME)))
$(eval $(call BuildPackage,python3-$(PKG_NAME)))
$(eval $(call BuildPackage,python3-$(PKG_NAME)-src))