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.
16938 Commits
1 Branch
46 MiB
Tree: f3d23d49b0
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'f3d23d49b0'
${ noResults }
openwrt-packages-dist/lang/python/django-constance/Makefile

67 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>
8 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>
8 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
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
8 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>
8 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>
8 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>
8 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>
8 years ago
​
​
django-constance: convert to python pkg format + add python3 variant Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
6 years ago
​
​
​
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>
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: 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>
5 years ago
seafile: import version 5.1.1 and its dependencies Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
8 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>
8 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:=4
  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. 	python3-django
  51.   VARIANT:=python3
  52.   MDEPENDS:=python3-django
  53. endef
  54. 

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

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

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