packages/lang/python/python3/files/python3-package.mk, branch openwrt-18.06

python,python3: export mk files outside of python package dirs

2018-01-10T21:01:51Z

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

python,python3: undo egg-info removal

2018-01-08T09:26:54Z

This reverts commits 4333d1dcbfd67dde4ca7d08717bc345cc424fbf8 and 074d2863be48c1a9093fffcda91f7a328bc7d0cb, making Python packages discoverable again by pkg_resources. Fixes #5361. Signed-off-by: Jeffery To

python,python3: add option to keep egg-info dirs for python packages

2017-10-03T07:40:26Z

That way some python packages can choose to keep their egg-info dirs, if they want to, or they're needed. Signed-off-by: Alexandru Ardelean

python,python3: add host python pip install support

2017-07-19T13:50:25Z

To install Python packages host side, that may be needed for a build. The intent, is to try to reduce host-side Python packages being installed via LEDE/OpenWrt build system. Because those seem like a pain to maintain. The idea is adapted from Yousong's `python-packages` package. Signed-off-by: Alexandru Ardelean

python,python3: define PyBuild/Compile & Py3Build/Compile

2017-07-07T15:07:10Z

Similar to LEDE/OpenWrt's Build/Compile/Default rule, and other similarities like this. This should allow Python packages to define PyBuild/Compile rules to do specific stuff per package. The advantage of using these (over just overriding Build/Compile) is the VARIANT mechanism that is in place to support packaging both for Python & Python3. So, PyBuild/Compile will get picked up for the Python variant build, and Py3Build/Compile will get picked up for the Python3 variant build. Signed-off-by: Alexandru Ardelean

python,python3: allow python packages to override Package//install rule

2017-05-19T14:16:39Z

Python packages try to enforce their own. For some cases this may not be desired. Signed-off-by: Alexandru Ardelean

python packages: move all things python under lang/python

2017-05-17T13:51:14Z

I admit this may be be a bit aggressive, but the lang folder is getting cluttered/filled up with Python, PHP, Perl, Ruby, etc. packages. Makes sense to try to group them into per-lang folders. I took the Pythons. Signed-off-by: Alexandru Ardelean