3ec5be3f51
This file was never truly necessary and has never actually been used in the history of Tailscale's open source releases. A Brief History of AUTHORS files --- The AUTHORS file was a pattern developed at Google, originally for Chromium, then adopted by Go and a bunch of other projects. The problem was that Chromium originally had a copyright line only recognizing Google as the copyright holder. Because Google (and most open source projects) do not require copyright assignemnt for contributions, each contributor maintains their copyright. Some large corporate contributors then tried to add their own name to the copyright line in the LICENSE file or in file headers. This quickly becomes unwieldy, and puts a tremendous burden on anyone building on top of Chromium, since the license requires that they keep all copyright lines intact. The compromise was to create an AUTHORS file that would list all of the copyright holders. The LICENSE file and source file headers would then include that list by reference, listing the copyright holder as "The Chromium Authors". This also become cumbersome to simply keep the file up to date with a high rate of new contributors. Plus it's not always obvious who the copyright holder is. Sometimes it is the individual making the contribution, but many times it may be their employer. There is no way for the proejct maintainer to know. Eventually, Google changed their policy to no longer recommend trying to keep the AUTHORS file up to date proactively, and instead to only add to it when requested: https://opensource.google/docs/releasing/authors. They are also clear that: > Adding contributors to the AUTHORS file is entirely within the > project's discretion and has no implications for copyright ownership. It was primarily added to appease a small number of large contributors that insisted that they be recognized as copyright holders (which was entirely their right to do). But it's not truly necessary, and not even the most accurate way of identifying contributors and/or copyright holders. In practice, we've never added anyone to our AUTHORS file. It only lists Tailscale, so it's not really serving any purpose. It also causes confusion because Tailscalars put the "Tailscale Inc & AUTHORS" header in other open source repos which don't actually have an AUTHORS file, so it's ambiguous what that means. Instead, we just acknowledge that the contributors to Tailscale (whoever they are) are copyright holders for their individual contributions. We also have the benefit of using the DCO (developercertificate.org) which provides some additional certification of their right to make the contribution. The source file changes were purely mechanical with: git ls-files | xargs sed -i -e 's/\(Tailscale Inc &\) AUTHORS/\1 contributors/g' Updates #cleanup Change-Id: Ia101a4a3005adb9118051b3416f5a64a4a45987d Signed-off-by: Will Norris <will@tailscale.com>
166 lines
6.1 KiB
Bash
Executable File
166 lines
6.1 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Copyright (c) Tailscale Inc & contributors
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
#
|
|
# gocross-wrapper.sh is a wrapper that can be aliased to 'go', which
|
|
# transparently runs the version of github.com/tailscale/go as specified repo's
|
|
# go.toolchain.rev file.
|
|
#
|
|
# It also conditionally (if TS_USE_GOCROSS=1) builds gocross and uses it as a go
|
|
# wrapper to inject certain go flags.
|
|
|
|
set -euo pipefail
|
|
|
|
if [[ "${CI:-}" == "true" && "${NOBASHDEBUG:-}" != "true" ]]; then
|
|
set -x
|
|
fi
|
|
|
|
if [[ "${OSTYPE:-}" == "cygwin" || "${OSTYPE:-}" == "msys" ]]; then
|
|
hash pwsh 2>/dev/null || { echo >&2 "This operation requires PowerShell Core."; exit 1; }
|
|
pwsh -NoProfile -ExecutionPolicy Bypass "${BASH_SOURCE%/*}/gocross-wrapper.ps1" "$@"
|
|
exit
|
|
fi
|
|
|
|
# Locate a bootstrap toolchain and (re)build gocross if necessary. We run all of
|
|
# this in a subshell because posix shell semantics make it very easy to
|
|
# accidentally mutate the input environment that will get passed to gocross at
|
|
# the bottom of this script.
|
|
(
|
|
repo_root="${BASH_SOURCE%/*}/../.."
|
|
|
|
# Figuring out if gocross needs a rebuild, as well as the rebuild itself, need
|
|
# to happen with CWD inside this repo. Since we're in a subshell entirely
|
|
# dedicated to wrangling gocross and toolchains, cd over now before doing
|
|
# anything further so that the rest of this logic works the same if gocross is
|
|
# being invoked from somewhere else.
|
|
cd "$repo_root"
|
|
|
|
# toolchain, set below, is the root of the Go toolchain we'll use to build
|
|
# gocross.
|
|
#
|
|
# It's set to either an explicit Go toolchain directory (if go.toolchain.rev has
|
|
# a value with a leading slash, for testing new toolchains), or otherwise in the
|
|
# common case it'll be "$HOME/.cache/tsgo/GITHASH" where GITHASH is the contents
|
|
# of the go.toolchain.rev file and the git commit of the
|
|
# https://github.com/tailscale/go release artifact to download.
|
|
toolchain=""
|
|
|
|
read -r REV <go.toolchain.rev
|
|
case "$REV" in
|
|
/*)
|
|
toolchain="$REV"
|
|
;;
|
|
*)
|
|
toolchain="$HOME/.cache/tsgo/$REV"
|
|
if [[ ! -f "$toolchain.extracted" ]]; then
|
|
mkdir -p "$HOME/.cache/tsgo"
|
|
rm -rf "$toolchain" "$toolchain.extracted"
|
|
|
|
echo "# Downloading Go toolchain $REV" >&2
|
|
|
|
# This works for linux and darwin, which is sufficient
|
|
# (we do not build tailscale-go for other targets).
|
|
HOST_OS=$(uname -s | tr A-Z a-z)
|
|
HOST_ARCH="$(uname -m)"
|
|
if [[ "$HOST_ARCH" == "aarch64" ]]; then
|
|
# Go uses the name "arm64".
|
|
HOST_ARCH="arm64"
|
|
elif [[ "$HOST_ARCH" == "x86_64" ]]; then
|
|
# Go uses the name "amd64".
|
|
HOST_ARCH="amd64"
|
|
fi
|
|
curl -f -L -o "$toolchain.tar.gz" "https://github.com/tailscale/go/releases/download/build-${REV}/${HOST_OS}-${HOST_ARCH}.tar.gz"
|
|
mkdir -p "$toolchain"
|
|
(cd "$toolchain" && tar --strip-components=1 -xf "$toolchain.tar.gz")
|
|
echo "$REV" >"$toolchain.extracted"
|
|
rm -f "$toolchain.tar.gz"
|
|
|
|
# Do some cleanup of old toolchains while we're here.
|
|
for hash in $(find "$HOME/.cache/tsgo" -maxdepth 1 -type f -name '*.extracted' -mtime 90 -exec basename {} \; | sed 's/.extracted$//'); do
|
|
echo "# Cleaning up old Go toolchain $hash" >&2
|
|
rm -rf "$HOME/.cache/tsgo/$hash"
|
|
rm -rf "$HOME/.cache/tsgo/$hash.extracted"
|
|
rm -rf "$HOME/.cache/tsgoroot/$hash"
|
|
done
|
|
fi
|
|
;;
|
|
esac
|
|
|
|
# gocross is opt-in as of 2025-06-16. See tailscale/corp#26717.
|
|
# It's primarily used for xcode builds, and a bit still for Windows.
|
|
# In the past we needed it for git version stamping on Linux etc, but
|
|
# Go does that itself nowadays.
|
|
if [ "${TS_USE_GOCROSS:-}" != "1" ]; then
|
|
exit 0 # out of subshell
|
|
fi
|
|
|
|
if [[ -d "$toolchain" ]]; then
|
|
# A toolchain exists, but is it recent enough to compile gocross? If not,
|
|
# wipe it out so that the next if block fetches a usable one.
|
|
want_go_minor="$(grep -E '^go ' "go.mod" | cut -f2 -d'.')"
|
|
have_go_minor=""
|
|
if [[ -f "$toolchain/VERSION" ]]; then
|
|
have_go_minor="$(head -1 "$toolchain/VERSION" | cut -f2 -d'.')"
|
|
fi
|
|
# Shortly before stable releases, we run release candidate
|
|
# toolchains, which have a non-numeric suffix on the version
|
|
# number. Remove the rc qualifier, we just care about the minor
|
|
# version.
|
|
have_go_minor="${have_go_minor%rc*}"
|
|
if [[ -z "$have_go_minor" || "$have_go_minor" -lt "$want_go_minor" ]]; then
|
|
rm -rf "$toolchain" "$toolchain.extracted"
|
|
fi
|
|
fi
|
|
|
|
# Binaries run with `gocross run` can reinvoke gocross, resulting in a
|
|
# potentially fancy build that invokes external linkers, might be
|
|
# cross-building for other targets, and so forth. In one hilarious
|
|
# case, cmd/cloner invokes go with GO111MODULE=off at some stage.
|
|
#
|
|
# Anyway, build gocross in a stripped down universe.
|
|
gocross_path="./gocross"
|
|
gocross_ok=0
|
|
wantver="$(git rev-parse HEAD)"
|
|
if [[ -x "$gocross_path" ]]; then
|
|
gotver="$($gocross_path gocross-version 2>/dev/null || echo '')"
|
|
if [[ "$gotver" == "$wantver" ]]; then
|
|
gocross_ok=1
|
|
fi
|
|
fi
|
|
if [[ "$gocross_ok" == "0" ]]; then
|
|
unset GOOS
|
|
unset GOARCH
|
|
unset GO111MODULE
|
|
unset GOROOT
|
|
export CGO_ENABLED=0
|
|
"$toolchain/bin/go" build -o "$gocross_path" -ldflags "-X tailscale.com/version.gitCommitStamp=$wantver" tailscale.com/tool/gocross
|
|
fi
|
|
) # End of the subshell execution.
|
|
|
|
repo_root="${BASH_SOURCE%/*}/../.."
|
|
|
|
# Some scripts/package systems set GOROOT even though they should only be
|
|
# setting $PATH. Stop them from breaking builds - go(1) respects GOROOT and
|
|
# so if it is left on here, compilation units depending on our Go fork will
|
|
# fail (such as those which depend on our net/ patches).
|
|
unset GOROOT
|
|
|
|
# gocross is opt-in as of 2025-06-16. See tailscale/corp#26717
|
|
# and comment above in this file.
|
|
if [ "${TS_USE_GOCROSS:-}" != "1" ]; then
|
|
read -r REV <"${repo_root}/go.toolchain.rev"
|
|
case "$REV" in
|
|
/*)
|
|
toolchain="$REV"
|
|
;;
|
|
*)
|
|
# If the prior subshell completed successfully, this toolchain location
|
|
# should be valid at this point.
|
|
toolchain="$HOME/.cache/tsgo/$REV"
|
|
;;
|
|
esac
|
|
exec "$toolchain/bin/go" "$@"
|
|
fi
|
|
|
|
exec "${repo_root}/gocross" "$@"
|