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

50 lines
1.3 KiB
Raw Normal View History

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
​
​
​
​
​
​
​
​
​
django1: bump to version 1.11.29 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
django1: Remove common package python-django1-common was added to allow both Python 2 and 3 versions of Django 1.11 to be installed at the same time. With the removal of Python 2, this package is no longer necessary. This removes this common package and updates the CONFLICTS value for the django package. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 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: 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
django1: bump to version 1.11.29 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 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: 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: 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
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>
4 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
django1: Remove common package python-django1-common was added to allow both Python 2 and 3 versions of Django 1.11 to be installed at the same time. With the removal of Python 2, this package is no longer necessary. This removes this common package and updates the CONFLICTS value for the django package. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 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
​
​
​
​
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>
4 years ago
python-packages: Clean up Makefiles This removes: * Python 3 variants (VARIANT:=python3) * "for Python3" from package titles * Package selection condition from package dependencies, e.g. +PACKAGE_python3-six:python3-light replaced with +python3-light * "Default" package information sections, e.g. Package/python-six/Default removed and package details merged into Package/python3-six * "(Variant for Python3)" from package descriptions Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 years ago
django1: Remove common package python-django1-common was added to allow both Python 2 and 3 versions of Django 1.11 to be installed at the same time. With the removal of Python 2, this package is no longer necessary. This removes this common package and updates the CONFLICTS value for the django package. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 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>
4 years ago
​
​
​
python-libraries: Remove Python 2 variants The Python 2 variants will be added to the abandoned packages feed. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 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>
4 years ago
​
django1: Remove common package python-django1-common was added to allow both Python 2 and 3 versions of Django 1.11 to be installed at the same time. With the removal of Python 2, this package is no longer necessary. This removes this common package and updates the CONFLICTS value for the django package. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 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>
4 years ago
django1: Remove common package python-django1-common was added to allow both Python 2 and 3 versions of Django 1.11 to be installed at the same time. With the removal of Python 2, this package is no longer necessary. This removes this common package and updates the CONFLICTS value for the django package. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 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
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>
4 years ago
​
​
​
 
  1. #

  2. # Copyright (C) Alexandru Ardelean <ardeleanalex@gmail.com>

  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:=django1
  11. PKG_VERSION:=1.11.29
  12. PKG_RELEASE:=4
  13. 

  14. PYPI_NAME:=Django
  15. PKG_HASH:=4200aefb6678019a0acf0005cd14cfce3a5e6b9b90d06145fcdd2e474ad4329c
  16. 

  17. PKG_MAINTAINER:=Alexandru Ardelean <ardeleanalex@gmail.com>
  18. PKG_LICENSE:=BSD-3-Clause
  19. PKG_LICENSE_FILES:=LICENSE LICENSE.python
  20. PKG_CPE_ID:=cpe:/a:djangoproject:django
  21. 

  22. include ../pypi.mk
  23. include $(INCLUDE_DIR)/package.mk
  24. include ../python3-package.mk
  25. 

  26. define Package/python3-django1
  27.   SUBMENU:=Python
  28.   SECTION:=lang
  29.   CATEGORY:=Languages
  30.   TITLE:=The web framework for perfectionists with deadlines.
  31.   URL:=https://www.djangoproject.com/
  32.   DEPENDS:= \

  33. 	+python3 \

  34. 	+python3-pytz
  35.   PROVIDES:=django
  36. endef
  37. 

  38. define Package/python3-django1/description
  39.   The web framework for perfectionists with deadlines (LTS 1.11 series).
  40. endef
  41. 

  42. define Py3Package/python3-django1/install
  43. 	$(INSTALL_DIR) $(1)/usr/bin
  44. 	$(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/django-admin.py \

  45. 		$(1)/usr/bin/django-admin
  46. endef
  47. 

  48. $(eval $(call Py3Package,python3-django1))
  49. $(eval $(call BuildPackage,python3-django1))
  50. $(eval $(call BuildPackage,python3-django1-src))