NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3dd0940081
kumquat-buildroot/package/docker-compose/Config.in

31 lines
1.1 KiB
Plaintext
Raw Normal View History

package: add docker-compose Python based multi-container orchestration for Docker. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-03-09 20:17:01 +01:00
config BR2_PACKAGE_DOCKER_COMPOSE
bool "docker-compose"
package/docker-compose: drop reference to BR2_PACKAGE_PYTHON And adjust the comments to clarify that the toolchain dependencies are from python3. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:50:36 +01:00
depends on BR2_USE_MMU # python3
depends on BR2_USE_WCHAR # python3
depends on BR2_TOOLCHAIN_HAS_THREADS # python3
depends on !BR2_STATIC_LIBS # python3
package/python-cryptography: bump version to 36.0.1 This version bump requires significant changes because python-cryptography is now partially implemented in Rust. This means that: - The C++ dependency is no longer needed. - We need to ensure we are on an architecture where Rust is available (BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS) - Almost all Python dependencies are no longer relevant, except for the python-cffi. - A number of environment variables are needed to make the Rust part build correctly. - We need to invoke the "cargo" download post-process hook to vendor the Cargo dependencies at download time. - We need to propagate to relatively significant reverse dependency tree the changes of dependencies on python-cryptography. Co-developed-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-06 22:43:30 +01:00
# python-paramiko -> python-cryptography
depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
package/python-bcrypt: bump to version 3.2.0 Python 2 is no longer supported, depend on python3 and propagate reverse dependency. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-07-09 01:03:00 +02:00
select BR2_PACKAGE_PYTHON3
package: add docker-compose Python based multi-container orchestration for Docker. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-03-09 20:17:01 +01:00
select BR2_PACKAGE_PYTHON_CACHED_PROPERTY # runtime
select BR2_PACKAGE_PYTHON_DOCOPT # runtime
package/docker-compose: bump version to 1.24.1 Fixes https://gitlab.com/buildroot.org/buildroot/-/jobs/332656041 The recent bump of a number of python packages broke docker-compose, as docker-compose specifies both minimum and maximum versions for (most of) its dependencies: Dependencies of docker-compse 1.20.1 (! = unmet): cached-property: < 2 (currently 1.51) docopt: < 0.7 (currently 0.6.2) ! pyyaml: < 4.0, patched to < 4.3 (currently 5.1.2) requests: < 2.19, patched to < 3 (currently 2.22.0) ! texttable: < 0.10 (currently 1.6.2) websocket-client: < 1.0 (currently 0.56.0) ! docker: < 4.0 (currently 4.1.0) dockerpty: < 0.5 (currently 0.4.1) six: < 2 (currently 1.12.0) jsonschema: < 3 (currently 2.5.1) enum34: < 2 (currently 1.1.6) backports.ssl-match-hostname: >= 3.5 (currently 3.7.0.1) ipaddress: >= 1.0.16 (currently 1.0.23) To fix this, bump docker-compose to the most recent release (1.24.1). This is unfortunately not enough, as our docker, pyyaml, requests and texttable packages are too new, so add 3 patches from upstream to relax the version checks of dependencies. Notice that patch 0003 is from https://github.com/docker/compose/pull/6623 and has not been merged yet. Discussions around the problem of these maximum versions of the dependencies and the fact that all downstream users have to patch it is ongoing here: https://github.com/docker/compose/issues/6756 docker-compose 1.24.1 added a requirement for ssh support in python-docker in: https://github.com/docker/compose/commit/7b82b2e8c721010b73f664e9d4657746a1fcd92b So add a dependency for python-paramiko and update the toolchain dependency for C++ (from python-paramiko -> python-cryptography) and adjust the toolchain configuration of the runtime test to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-10-26 16:05:24 +02:00
select BR2_PACKAGE_PYTHON_PARAMIKO # runtime
package: add docker-compose Python based multi-container orchestration for Docker. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-03-09 20:17:01 +01:00
select BR2_PACKAGE_PYTHON_PYYAML # runtime
select BR2_PACKAGE_PYTHON_REQUESTS # runtime
select BR2_PACKAGE_PYTHON_TEXTTABLE # runtime
select BR2_PACKAGE_PYTHON_WEBSOCKET_CLIENT # runtime
select BR2_PACKAGE_PYTHON_DOCKER # runtime
select BR2_PACKAGE_PYTHON_DOCKERPTY # runtime
select BR2_PACKAGE_PYTHON_SIX # runtime
select BR2_PACKAGE_PYTHON_JSONSCHEMA # runtime
help
Multi-container orchestration for Docker.
https://www.docker.com/
package/python-cryptography: bump version to 36.0.1 This version bump requires significant changes because python-cryptography is now partially implemented in Rust. This means that: - The C++ dependency is no longer needed. - We need to ensure we are on an architecture where Rust is available (BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS) - Almost all Python dependencies are no longer relevant, except for the python-cffi. - A number of environment variables are needed to make the Rust part build correctly. - We need to invoke the "cargo" download post-process hook to vendor the Cargo dependencies at download time. - We need to propagate to relatively significant reverse dependency tree the changes of dependencies on python-cryptography. Co-developed-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-06 22:43:30 +01:00
comment "docker-compose needs a toolchain w/ wchar, threads, dynamic library"
package: add docker-compose Python based multi-container orchestration for Docker. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-03-09 20:17:01 +01:00
depends on BR2_USE_MMU
package/python-cryptography: bump version to 36.0.1 This version bump requires significant changes because python-cryptography is now partially implemented in Rust. This means that: - The C++ dependency is no longer needed. - We need to ensure we are on an architecture where Rust is available (BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS) - Almost all Python dependencies are no longer relevant, except for the python-cffi. - A number of environment variables are needed to make the Rust part build correctly. - We need to invoke the "cargo" download post-process hook to vendor the Cargo dependencies at download time. - We need to propagate to relatively significant reverse dependency tree the changes of dependencies on python-cryptography. Co-developed-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-06 22:43:30 +01:00
depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
package/docker-compose: bump version to 1.24.1 Fixes https://gitlab.com/buildroot.org/buildroot/-/jobs/332656041 The recent bump of a number of python packages broke docker-compose, as docker-compose specifies both minimum and maximum versions for (most of) its dependencies: Dependencies of docker-compse 1.20.1 (! = unmet): cached-property: < 2 (currently 1.51) docopt: < 0.7 (currently 0.6.2) ! pyyaml: < 4.0, patched to < 4.3 (currently 5.1.2) requests: < 2.19, patched to < 3 (currently 2.22.0) ! texttable: < 0.10 (currently 1.6.2) websocket-client: < 1.0 (currently 0.56.0) ! docker: < 4.0 (currently 4.1.0) dockerpty: < 0.5 (currently 0.4.1) six: < 2 (currently 1.12.0) jsonschema: < 3 (currently 2.5.1) enum34: < 2 (currently 1.1.6) backports.ssl-match-hostname: >= 3.5 (currently 3.7.0.1) ipaddress: >= 1.0.16 (currently 1.0.23) To fix this, bump docker-compose to the most recent release (1.24.1). This is unfortunately not enough, as our docker, pyyaml, requests and texttable packages are too new, so add 3 patches from upstream to relax the version checks of dependencies. Notice that patch 0003 is from https://github.com/docker/compose/pull/6623 and has not been merged yet. Discussions around the problem of these maximum versions of the dependencies and the fact that all downstream users have to patch it is ongoing here: https://github.com/docker/compose/issues/6756 docker-compose 1.24.1 added a requirement for ssh support in python-docker in: https://github.com/docker/compose/commit/7b82b2e8c721010b73f664e9d4657746a1fcd92b So add a dependency for python-paramiko and update the toolchain dependency for C++ (from python-paramiko -> python-cryptography) and adjust the toolchain configuration of the runtime test to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-10-26 16:05:24 +02:00
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || \
package/python-cryptography: bump version to 36.0.1 This version bump requires significant changes because python-cryptography is now partially implemented in Rust. This means that: - The C++ dependency is no longer needed. - We need to ensure we are on an architecture where Rust is available (BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS) - Almost all Python dependencies are no longer relevant, except for the python-cffi. - A number of environment variables are needed to make the Rust part build correctly. - We need to invoke the "cargo" download post-process hook to vendor the Cargo dependencies at download time. - We need to propagate to relatively significant reverse dependency tree the changes of dependencies on python-cryptography. Co-developed-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-06 22:43:30 +01:00
BR2_STATIC_LIBS
Reference in New Issue Copy Permalink