The release .tar.gz held the four binaries and their translations only, and the service unit pointed at /usr/bin/pdfs, so it was no install on its own. It now carries a /usr-like tree (bin, share, the user unit, the tray's autostart entry) and install.sh, which installs it into ~/.local without root: - checks the libraries with ldd and names the packages to install per distribution, and that fusermount3 is there and setuid; - refuses to install next to a package of the client; - rewrites Exec= and ExecStart= to absolute paths, since ~/.local/bin is often not on a session's PATH; - keeps a manifest, removes what an older version left, restarts a running service on update, and --uninstall leaves settings alone. packaging/tarball/build.sh lays the tarball out and test.sh installs, updates and uninstalls it in a throwaway home; the release job runs both, CI runs shellcheck on them. The app looks for its translations in share/locale beside its own bin directory and starts the tray from there, so nothing needs PDFS_LOCALEDIR or the PATH. The -bin AUR package takes every file from the new tarball instead of raw.githubusercontent.com. INSTALL.md documents the tarball and layering the COPR package on Fedora Atomic.
AUR packages
Source of truth for the three AUR packages of this project. Each subdirectory is
the full content of one AUR git repository (pkgbase = directory name):
| Directory | What it does | AUR repository |
|---|---|---|
proton-drive-for-linux |
Builds the latest tagged release from source | ssh://aur@aur.archlinux.org/proton-drive-for-linux.git |
proton-drive-for-linux-git |
Builds main from git |
ssh://aur@aur.archlinux.org/proton-drive-for-linux-git.git |
proton-drive-for-linux-bin |
Installs the binaries from the GitHub release | ssh://aur@aur.archlinux.org/proton-drive-for-linux-bin.git |
The three packages conflict with each other and with the in-tree
packaging/PKGBUILD package (proton-drive-linux), and every one of them
provides proton-drive-for-linux, proton-drive-linux, and pdfs.
Each directory tracks only PKGBUILD, .SRCINFO, .gitignore, LICENSE and
proton-drive.install (a link to packaging/proton-drive.install, copied as a file on push)
(the 0BSD license of the packaging sources, per
RFC40); the
.gitignore ignores everything else so downloaded sources, src/, pkg/, and
built packages never reach the AUR.
Releasing a new version
.github/workflows/aur.yml does this automatically:
- On a release tag,
release.ymlcalls it after the GitHub release is published. It runs./update.sh <version>, pushes all three packages with./push.sh, and commits the updated recipes back tomainaschore(aur): update packages to <version>. - On a push to
mainthat changesproton-drive-for-linux-git/, it regenerates that package's.SRCINFOand pushes only the -git package. - By hand, run the workflow from the Actions tab. Give a version to publish a release, or leave it empty to publish only the -git package.
It needs the AUR_SSH_PRIVATE_KEY repository secret: a private key whose public
half is registered with the AUR account.
To do the same by hand:
- Tag and publish the upstream release, so the source tarball and the
proton-drive-linux-<version>-x86_64.tar.gzrelease asset exist. - Run
./update.sh <version>— it rewritespkgver, resetspkgrel=1, refreshes the checksums of the release-based packages, and regenerates every.SRCINFO. - Build and inspect the packages in a clean chroot:
cd proton-drive-for-linux && pkgctl build --clean(needsdevtools). - Commit here, then publish with
./push.sh(or./push.sh proton-drive-for-linux-binfor a single package).
proton-drive-for-linux-git carries a pkgver() function, so its pkgver is
computed at build time; do not push a commit that only bumps it. This is why new
commits on main do not trigger an AUR push.
Requirements for pushing
An SSH key registered with the AUR account and an entry in ~/.ssh/config:
Host aur.archlinux.org
IdentityFile ~/.ssh/aur
User aur
push.sh creates a scratch clone of the AUR repository, copies the tracked
files over it, commits, and pushes to master.