| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | python/python3: fix .dist-info missing for setuptools and pip | Jeffery To | 2018-12-22 | 1 | -6/+2 |
| | | | | | | | | Without .dist-info (similar to .egg-info), setuptools and pip are not discoverable by pkg_resources. Signed-off-by: Jeffery To <jeffery.to@gmail.com> | ||||
| * | python: update to version 2.7.15 | Alexandru Ardelean | 2018-05-03 | 1 | -3/+9 |
| | | | | | | | | | | | | This also updates pip and setuptools. With this occasion, they also get PKG_RELEASEs of their own. Dropped patch 011-remove-setupterm-definition.patch Manually re-applied 005-fix-bluetooth-support.patch Ran make package/python/refresh to refresh other patches. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com> | ||||
| * | python,python3: export mk files outside of python package dirs | Alexandru Ardelean | 2018-01-10 | 1 | -0/+13 |
| Since `lang/python` is it's own folder of Python packages (for both Python 2 & 3), and these build rules are needed in a lot of packages [especially Python packages], putting them here makes sense architecturally, to be shared. This also helps get rid of the `include_mk` construct which relies on OpenWrt core to provide, and seems like a broken design idea that has persisted for a while. Reason is: it requires that Python 2/3 be built to provide these mk files for other Python packages, which seems like a bad idea. Long-term, there could be an issue where some other feeds would require these mk files [e.g. telephony] for some Python packages. We'll see how we handle this a bit later. For now we limit this to this feed. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com> | |||||
