packages/lang/python/python-package.mk, branch openwrt-18.06Community maintained packages for OpenWrthttp://x-nagi.com/cgit/packages/atom?h=openwrt-18.062019-08-08T11:38:37Zpython,python3: Fix overridden usr/bin symlinks2019-08-08T11:38:37ZJeffery Tojeffery.to@gmail.com2019-03-31T11:11:15Zurn:sha1:af975f0f30b433054d593de2c76a892cc37ea7ad
Currently, all files in usr/bin (presumably all Python scripts) are run
through sed to replace the shebang; sed will overwrite the file whether
or not a match is found. This causes symlinks to be overridden and made
into copies of their targets. python[3]-base and python[3]-dev are
affected by this.
This adds the --follow-symlinks flag to sed, in addition to using
$(SED), so that symlinks are not overridden.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
python,python3: fix recursive deps caused by dangling DEPENDS2018-01-17T15:30:48ZAlexandru Ardeleanardeleanalex@gmail.com2018-01-17T15:30:48Zurn:sha1:6494642caf801ea2f3d3be08d4dee9372c99cc5d
For python `src` packages we should clear out the DEPENDS
to prevent recursive deps from happening.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Merge pull request #5457 from jefferyto/python-pkg-setup-args-vars2018-01-17T14:07:41ZHannu Nymanhannu.nyman@iki.fi2018-01-17T14:07:41Zurn:sha1:f6f239f15968f3cffe76e1a9b64ad0752cfc66b6
python,python3: add vars to customize setup arguments / variablespython,python3: disable dependencies between python src packages2018-01-16T14:18:47ZAlexandru Ardeleanardeleanalex@gmail.com2018-01-15T12:10:00Zurn:sha1:63dfa198127de1ac0411a5833716cafc30060f12
Related to:
https://github.com/openwrt/packages/issues/5424
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
python,python3: add vars to customize setup arguments / variables2018-01-15T20:10:49ZJeffery Tojeffery.to@gmail.com2018-01-15T20:10:49Zurn:sha1:021271c1d3b1f9ee4ee4637e04118e3bb1ff89be
This adds:
* PYTHON_PKG_SETUP_ARGS
* PYTHON_PKG_SETUP_VARS
* PYTHON3_PKG_SETUP_ARGS
* PYTHON3_PKG_SETUP_VARS
to customize Python package setup arguments / environment variables.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
python,python3: merge package install scripts2018-01-10T21:06:22ZAlexandru Ardeleanardeleanalex@gmail.com2018-01-10T07:52:18Zurn:sha1:f4c098cc85417fdfc39476d0b8fda6981ac3c265
The only difference just a parameter for Python3
[ -b to compile bytecodes in legacy mode ].
No need to keep 2 almost identical files now
that they're exported.
I'm a bit scared of that param, since it may get
removed at some point.
But let's see until then.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
python,python3: simplify path to install shell-script2018-01-10T21:01:51ZAlexandru Ardeleanardeleanalex@gmail.com2018-01-10T07:43:00Zurn:sha1:57987b699b4a02552f2ff916e797a2e930c63d25
Now that all files are exported, it makes sense
to just reference the script directly.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
python,python3: export mk files outside of python package dirs2018-01-10T21:01:51ZAlexandru Ardeleanardeleanalex@gmail.com2018-01-10T07:29:41Zurn:sha1:ccdc6bc530444283a510ceb6a50878493fe356f2
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>