mirror of
https://github.com/docker/docker-ce-packaging.git
synced 2025-04-19 00:04:03 +03:00
59 lines
2.7 KiB
Makefile
59 lines
2.7 KiB
Makefile
ARCH=$(shell uname -m)
|
|
|
|
# These are the architecture formats as used in release-packaging Jenkinsfile
|
|
# This is an ugly chimera, nobody uses this combination of dpkg and uname formats
|
|
# Why don't we pick one format and stick with it? Because at the time of writing
|
|
# it was deemed too risky/involving too many changes across repos to change architecture
|
|
# formats in release-packaging Jenkinsfile. But someone please do it.
|
|
# Why do we need to list this here? Because I haven't been able to figure out how
|
|
# to do Makefile rules with multiple patterns. (See how it's used in {deb,rpm}/Makefile)
|
|
# Adding new architectures or changing the format in release-packaging will prevent make
|
|
# from finding the corresponding rule unless this list is updated.
|
|
# Or Jenkinsfiles/Makefiles removed (🎵 Gotta have faith-a-faith-a-faith... 🎵)
|
|
ARCHES:=amd64 aarch64 armhf armel s390x ppc64le
|
|
|
|
BUILDTIME=$(shell date -u -d "@$${SOURCE_DATE_EPOCH:-$$(date +%s)}" --rfc-3339 ns 2> /dev/null | sed -e 's/ /T/')
|
|
CHOWN:=docker run --rm -v $(CURDIR):/v -w /v alpine chown
|
|
DEFAULT_PRODUCT_LICENSE:=Community Engine
|
|
PACKAGER_NAME?=
|
|
DOCKER_GITCOMMIT:=abcdefg
|
|
GO_VERSION:=1.23.8
|
|
PLATFORM=Docker Engine - Community
|
|
SHELL:=/bin/bash
|
|
VERSION?=0.0.1-dev
|
|
|
|
# DOCKER_CLI_REPO and DOCKER_ENGINE_REPO define the source repositories to clone
|
|
# the source from. These can be overridden to build from a fork.
|
|
DOCKER_CLI_REPO ?= https://github.com/docker/cli.git
|
|
DOCKER_ENGINE_REPO ?= https://github.com/docker/docker.git
|
|
DOCKER_COMPOSE_REPO ?= https://github.com/docker/compose.git
|
|
DOCKER_BUILDX_REPO ?= https://github.com/docker/buildx.git
|
|
|
|
# REF can be used to specify the same branch or tag to use for *both* the CLI
|
|
# and Engine source code. This can be useful if both the CLI and Engine have a
|
|
# release branch with the same name (e.g. "19.03"), or of both repositories have
|
|
# tagged a release with the same version.
|
|
#
|
|
# For other situations, specify DOCKER_CLI_REF and/or DOCKER_ENGINE_REF separately.
|
|
REF ?= HEAD
|
|
DOCKER_CLI_REF ?= $(REF)
|
|
DOCKER_ENGINE_REF ?= $(REF)
|
|
# DOCKER_COMPOSE_REF is the version of compose to package. It usually is a tag,
|
|
# but can be a valid git reference in DOCKER_COMPOSE_REPO.
|
|
DOCKER_COMPOSE_REF ?= v2.35.1
|
|
# DOCKER_BUILDX_REF is the version of compose to package. It usually is a tag,
|
|
# but can be a valid git reference in DOCKER_BUILDX_REPO.
|
|
DOCKER_BUILDX_REF ?= v0.23.0
|
|
|
|
# Use "stage" to install dependencies from download-stage.docker.com during the
|
|
# verify step. Leave empty or use any other value to install from download.docker.com
|
|
VERIFY_PACKAGE_REPO ?= prod
|
|
|
|
# Optional flags like --platform=linux/armhf
|
|
VERIFY_PLATFORM ?=
|
|
|
|
export BUILDTIME
|
|
export DEFAULT_PRODUCT_LICENSE
|
|
export PACKAGER_NAME
|
|
export PLATFORM
|