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

55 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.25 Signed-off-by: Alexandru Ardelean <ardeleanalex@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
​
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.25 Signed-off-by: Alexandru Ardelean <ardeleanalex@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
​
​
​
​
​
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
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
 
  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.25
  12. PKG_RELEASE:=1
  13. 

  14. PYPI_NAME:=Django
  15. PKG_HASH:=5314e8586285d532b7aa5c6d763b0248d9a977a37efec86d30f0212b82e8ef66
  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 ../python-package.mk
  25. 

  26. define Package/django1/Default
  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.   MENU:=1
  33. endef
  34. 

  35. define Package/python-django1
  36. $(call Package/django1/Default)
  37.   DEPENDS:= \

  38. 	+PACKAGE_python-django1:python \

  39. 	+PACKAGE_python-django1:python-pytz
  40.   VARIANT:=python
  41.   CONFLICTS:=python3-django
  42. endef
  43. 

  44. define Package/python-django1/description
  45.     The web framework for perfectionists with deadlines (LTS 1.11 series).
  46.     Python2 only.
  47. endef
  48. 

  49. $(eval $(call PyPackage,python-django1))
  50. define Package/python-django1-src +=
  51. 

  52.   MDEPENDS:=python-django1
  53. endef
  54. $(eval $(call BuildPackage,python-django1))
  55. $(eval $(call BuildPackage,python-django1-src))