Currently we have some license issues. We are working on it.

Verified Commit 1c1edeb6 authored by noplanman's avatar noplanman
Browse files

Build using Python 3.5 (like official borg binaries) and use new armv5e arch name.

parent 2ec1a334
......@@ -8,7 +8,7 @@ stages:
armv5:
extends: .main
variables: {ARCH: armel, NAME: "borg-${CI_COMMIT_TAG}-armv5"}
variables: {ARCH: armv5e, NAME: "borg-${CI_COMMIT_TAG}-armv5"}
armv6:
extends: .main
......
ARG BORG_ARCH
FROM balenalib/${BORG_ARCH}-python:3.6-jessie-run
FROM balenalib/${BORG_ARCH}-python:3.5-jessie-run
ARG BORG_ARCH
ARG BORG_VERSION=1.1.10
......
# Base image to build the binaries from, based on BorgBackup version 1.1.0
ARG BORG_ARCH
FROM balenalib/${BORG_ARCH}-python:3.6-jessie-run
FROM balenalib/${BORG_ARCH}-python:3.5-jessie-run
ARG BORG_ARCH
......
......@@ -58,6 +58,8 @@ This is basically done by following the flow of setting up a [BorgBackup develop
When using the base images created by `build-base.sh`, instead of using the normal `Dockerfile`, you can set the `BBB_HOT` environment variable to any value, which makes the build script use `Dockerfile.hot`.
The build then starts off with the prebuilt base image, speeding up the build tremendously.
Builds are based on the Python 3.5 images on Debian Jessie.
### Extract
The `extract.sh` script extracts the built binary from the image created using `build.sh`.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment