LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
18521 Commits
1 Branch
46 MiB
Tree: 417d7e415f
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '417d7e415f'
${ noResults }
openwrt-packages-dist/lang/python/django-constance/Makefile

66 lines
1.8 KiB
Raw Normal View History

seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
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>
8 years ago
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
​
​
​
​
​
​
​
django-constance: Update to 2.3.1 Signed-off-by: Rosen Penev <rosenp@gmail.com>
6 years ago
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>
5 years ago
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
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>
5 years ago
django-constance: Update to 2.3.1 Signed-off-by: Rosen Penev <rosenp@gmail.com>
6 years ago
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>
5 years ago
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>
6 years ago
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>
5 years ago
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
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>
5 years ago
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
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>
7 years ago
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
​
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
​
​
​
​
​
​
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
​
​
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>
5 years ago
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
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>
5 years ago
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
​
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
​
​
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
​
​
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>
5 years ago
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
​
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
python-packages: Clean up Makefiles * Replace $(PKG_NAME) with package name in call, define, and eval lines * Remove extra "define" in $(call define Package/.../description) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
9 years ago
​
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
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>
5 years ago
​
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
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>
5 years ago
 
  1. #

  2. # Copyright (C) 2007-2017 OpenWrt.org

  3. #

  4. # This is free software, licensed under the GNU General Public License v2.

  5. # See /LICENSE for more information.

  6. #

  7. 

  8. include $(TOPDIR)/rules.mk
  9. 

  10. PKG_NAME:=django-constance
  11. PKG_VERSION:=2.3.1
  12. PKG_RELEASE:=5
  13. 

  14. PYPI_NAME:=$(PKG_NAME)
  15. PKG_HASH:=a49735063b2c30015d2e52a90609ea9798da722ed070f091de51714758a5d018
  16. 

  17. PKG_MAINTAINER:=Alexandru Ardelean <ardeleanalex@gmail.com>
  18. PKG_LICENSE:=BSD-3-Clause
  19. 

  20. include ../pypi.mk
  21. include $(INCLUDE_DIR)/package.mk
  22. include ../python-package.mk
  23. include ../python3-package.mk
  24. 

  25. define Package/python-django-constance/Default
  26.   SUBMENU:=Python
  27.   SECTION:=lang
  28.   CATEGORY:=Languages
  29.   TITLE:=Django live settings with pluggable backends, including Redis.
  30.   URL:=https://github.com/jazzband/django-constance
  31. endef
  32. 

  33. define Package/python-django-constance
  34. $(call Package/python-django-constance/Default)
  35.   DEPENDS:= \

  36. 	+PACKAGE_python-django-constance:python \

  37. 	python-django1
  38.   VARIANT:=python
  39.   MDEPENDS:=python-django1
  40. endef
  41. 

  42. define Package/python-django-constance/description
  43.   Django live settings with pluggable backends, including Redis.
  44. endef
  45. 

  46. define Package/python3-django-constance
  47. $(call Package/python-django-constance/Default)
  48.   DEPENDS:= \

  49. 	+PACKAGE_python3-django-constance:python3 \

  50. 	+PACKAGE_python3-django-constance:python3-django1
  51.   VARIANT:=python3
  52. endef
  53. 

  54. define Package/python3-django-constance/description
  55. $(call Package/python-django-constance/description)
  56. .
  57. (Variant for Python3)
  58. endef
  59. 

  60. $(eval $(call PyPackage,python-django-constance))
  61. $(eval $(call BuildPackage,python-django-constance))
  62. $(eval $(call BuildPackage,python-django-constance-src))
  63. 

  64. $(eval $(call Py3Package,python3-django-constance))
  65. $(eval $(call BuildPackage,python3-django-constance))
  66. $(eval $(call BuildPackage,python3-django-constance-src))