buildroot/package/python-pyro, branch 2019.02-op-build

package/*/Config.in: fix help text check-package warnings

2017-12-18T08:22:54+00:00

This commit fixes the warnings reported by check-package on the help text of all package Config.in files, related to the formatting of the help text: should start with a tab, then 2 spaces, then at most 62 characters. The vast majority of warnings fixed were caused by too long lines. A few warnings were related to spaces being used instead of a tab to indent the help text. Signed-off-by: Thomas Petazzoni

python-pyro: switch to setuptools instead of distutils

2017-07-13T08:54:24+00:00

python-pyro can use setuptools instead of distutils, and using setuptools is generally preferred. In addition, using setuptools allows to make sure the package will continue to build when we will adjust the PYTHONPATH variable to no longer point to target Python modules. Without such a change to setuptools, the build would fail with: ===================================================================== running install Checking .pth file support in /home/test/buildroot/output/target/usr/lib/python2.7/site-packages/ /home/test/buildroot/output/host/bin/python -E -c pass TEST FAILED: /home/test/buildroot/output/target/usr/lib/python2.7/site-packages/ does NOT support .pth files error: bad install directory or PYTHONPATH You are attempting to install a package to a directory that is not on PYTHONPATH and which Python does not read ".pth" files from. The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /home/test/buildroot/output/target/usr/lib/python2.7/site-packages/ and your PYTHONPATH environment variable currently contains: '/home/test/buildroot/output/target/usr/lib/python2.7/sysconfigdata/' Here are some of your options for correcting the problem: * You can choose a different installation directory, i.e., one that is on PYTHONPATH or supports .pth files * You can add the installation directory to the PYTHONPATH environment variable. (It must then also be on PYTHONPATH whenever you run Python and want to use the package(s) you are installing.) * You can set up the installation directory to support ".pth" files by using one of the approaches described here: https://setuptools.readthedocs.io/en/latest/easy_install.html#custom-installation-locations ===================================================================== Signed-off-by: Thomas Petazzoni Reviewed-by: Yegor Yefremov Signed-off-by: Thomas Petazzoni

python-pyro: bump to version 3.16

2017-03-02T20:54:15+00:00

Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

package/python-pyro: add hash file

2016-06-19T20:03:33+00:00

Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

.mk files: bulk aligment and whitespace cleanup of assignments

2014-10-07T13:00:28+00:00

The Buildroot coding style defines one space around make assignments and does not align the assignment symbols. This patch does a bulk fix of offending packages. The package infrastructures (or more in general assignments to calculated variable names, like $(2)_FOO) are not touched. Alignment of line continuation characters (\) is kept as-is. The sed command used to do this replacement is: find * -name "*.mk" | xargs sed -i \ -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$#\1 \2#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$[^\\]\+$$#\1 \2 \3#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$[^\\ \t]\+\s*\\$\s*$#\1 \2 \3#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$$\s*\\$#\1 \2\3#' Brief explanation of this command: ^$[A-Z0-9a-z_]\+$ a regular variable at the beginning of the line $[?:+]\?=$ any assignment character =, :=, ?=, += $[^\\]\+$ any string not containing a line continuation $[^\\ \t]\+\s*\\$ string, optional whitespace, followed by a line continuation character $\s*\\$ optional whitespace, followed by a line continuation character Hence, the first subexpression handles empty assignments, the second handles regular assignments, the third handles regular assignments with line continuation, and the fourth empty assignments with line continuation. This expression was tested on following test text: (initial tab not included) FOO = spaces before FOO = spaces before and after FOO = tab before FOO = tab and spaces before FOO = tab after FOO = tab and spaces after FOO = spaces and tab after FOO = \ FOO = bar \ FOO = bar space \ FOO = \ GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse FOO += spaces before FOO ?= spaces before and after FOO := FOO = FOO = FOO = FOO = $(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C AT91BOOTSTRAP3_DEFCONFIG = \ AXEL_DISABLE_I18N=--i18n=0 After this bulk change, following manual fixups were done: - fix line continuation alignment in cegui06 and spice (the sed expression leaves the number of whitespace between the value and line continuation character intact, but the whitespace before that could have changed, causing misalignment. - qt5base was reverted, as this package uses extensive alignment which actually makes the code more readable. Finally, the end result was manually reviewed. Signed-off-by: Thomas De Schampheleire Cc: Yann E. Morin Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard

package: remove the trailing slash sign from _SITE variable

2014-07-31T21:17:46+00:00

Since the trailing slash is stripped from $($(PKG)_SITE) by pkg-generic.mk: $(call DOWNLOAD,$($(PKG)_SITE:/=)/$($(PKG)_SOURCE)) so it is redundant. This patch removes it from $(PKG)_SITE variable for BR consistency. Signed-off-by: Jerzy Grzegorek Signed-off-by: Thomas Petazzoni

python-pyro: convert to the Python package infrastructure

2013-12-15T12:38:37+00:00

Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

package/python-pyro: adding Pyro 3.14

2013-07-22T15:22:33+00:00

[Peter: fix LICENSE_FILES tag, adjust upstream URL] Signed-off-by: Fabien Marteau Signed-off-by: Peter Korsgaard