| Commit message (Collapse) | Author | Age |
... | |
| |/
|/|
| |
| |
| |
| |
| |
| | |
This was a bit overdue.
I did not know about this methodology.
Reduces patch fuzz.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|\ \
| | |
| | | |
python-cffi: upgrade to 1.10.0 (together with dependencies)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
And drop the host-build.
This was needed, simply to cross-build the package.
I'm not a religious man, but "praise the lord" for
dropping this :D
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Not used, and will not be used.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should hopefully reduce weird behaviour caused
by the host system.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Depending on execution order the `python-package-install.sh`
script would return a non-zero err code.
So, this enforces that all commands in the script
don't fail (via the `set -e` directive).
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Python provides the WORDS_BIGENDIAN macro, use it to figure out the
native endian of the host.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
auto-endian auf UTF-16 doesn't work with all drivers, some fail to
interpret the byte-order-marking. Hence explicitely use UTF16BE on
big-endian systems and UTF16LE otherwise.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| |
| |
| |
| | |
Flask is a microframework for Python based on Werkzeug, Jinja 2 and
good intentions. And before you ask: It.s BSD licensed!
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| |
| |
| | |
Bump PKG_REV and remove obsolete PKG_MD5SUM while at it.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| |
| |
| | |
Update source to version 3.12 and build for both, python and python3.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
|\ \
| | |
| | | |
python,python3: rename PyBuild/Compile rules & remove .egg-info from packages
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
And depend on python-light only if python-lxml is selected.
Same thing for python3-lxml.
Otherwise, this builds both Python & Python3 intepreters.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
They don't seem needed, and makes packages a bit smaller
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
|\ \ \
| | | |
| | | | |
pyodbc: fix python-pyodbc variant ; wasn't working
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Python3 variant was working fine.
Also add add PACKAGE_python-pyodbc conditional depend for python packages
Otherwise, both Python & Python3 interpreters get built,
even tho only one variant is selected.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes: https://github.com/openwrt/packages/issues/4548
When running parallel jobs, there are chances
that the Build/InstallDev rule may run before
the Host/Install rule and fail the build.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If you build python/python3 and later decide to build
python(3)-setuptools and/or python(3)-pip, the build won't
re-run without adding `CONFIG_PACKAGE_python(3)-setuptools`
and `CONFIG_PACKAGE_python(3)-pip`.
Seems to resolve issue:
https://github.com/openwrt/packages/issues/4529
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A suggestion from comment (from Philip Prindeville):
https://github.com/openwrt/packages/issues/4529#issuecomment-312518121
Avoids some escaping of slashes.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Seems it's called underlinking that's happening only
on Ubuntu 12.04 with libressl (that comes from LEDE's
tools folder).
Link here:
https://ubuntuforums.org/showthread.php?t=1870586
I'm still reading about this a bit.
Since I don't really get it.
But applying that fix (as in the link) seems to fix compiling
on Ubuntu 12.04, and tried also on 16.04 (to make sure).
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The Build/InstallDev rule is activated only for target builds.
But if someone needs only the host Python, then
these files need to be installed in this phase, and not Build/InstallDev
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OVS has PKG_BUILD_DEPENDS:=python-six/host as dep.
But that doesn't seem to work, since the PKG_NAME:=six
So, this change renames the PKG_NAME to python-six, to
make it clear it's Python package.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If there is only Python bytecodes, then
the __init__.py script will be concatenated, and
the __init__.pyc as well.
This is becase this bit `path = os.path.join(path, '__init__'+extension)`
is iterated twice.
This is a bug in Python3, also because we ship bytecodes
instead of source code [ with Python & Python3 ].
Python is not affected.
Reported-by: Mirko Vogt <mirko@nanl.de>
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
| |
This package requires libxml2 & libxslt to be built, has some
C code so it's not installable via pip.
It needs cross-compilation.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
| |
Needed for Open vSwitch's python libs.
And build.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is in essence fixes pip3.
That means pip3 will ship without Python byte-codes
for a while, until I'll find a better way to fix it.
I couldn't think of a not-very hack-ish way of doing it.
The only draw-back of this, will be that pip3 will run
a bit slower ; but that should be ok for a while.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
python3-pip & python3-setuptools have slightly
different installation mechanisms.
We need to remove the __pycache__ folders.
Seems they're generated.
This also reduces the size of the python3-pip &
python3-setuptools packages.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
| |
Python packages try to enforce their own.
For some cases this may not be desired.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <ardeleanalex@gmail.com>
|
|
|
|
| |
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Well, they're not yet compiled, but in the next commit
they should be.
People have been complaining [citation needed] to me
via email or via Github that Python's performance is crap
because it packages sources directly and they're not compiled.
And Python has to compile the sources on each run, and
on-the-fly.
Allowing compilation caching is also a no-no, because
I'll get complaints that the flash storage fills up
whenever a Python app runs.
So, to give the user a choice, the new de-facto packaging
for Python packages will be:
* ship compiled + [ preferably ] optimized files
* package sources separately
The problem is that this doubles the number of packages
in LEDE/OpenWrt, but build-times should not suffer a big
hit, since the compilation is done once, and the
install phase should not be too intensive.
Oh, and people don't need ship source packages if
they don't want to.
To do that, a packager needs to just call
`$(eval $(call BuildPackage,python-<package>-src))`
The `python-` prefix is important.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
| |
We'll control in the install phase what we ship [byte-codes or source files]
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
| |
Well, this slipped by for some time.
This should make the Python core packages even more lighter.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
| |
Both want to install libpython.so.
python-dev should install libpython.a
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
| |
install rules
So that we can process Python sources installed
by those rules, if we need to.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
| |
Cleanup.
And preparation for adding a bit more functionality.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
| |
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|