0 Fork 0

mirror of https://github.com/narrrl/proton-drive-linux.git synced 2026-11-04 00:47:00 +01:00

Files

T

nvrl 90e110e893 feat(fuse,core): thumbnails for videos and for our own uploads

Videos without a server thumbnail fell through to the local fallback,
which downloaded the whole file, failed to decode it as an image and
wrote the video off for good. Grab one frame with ffmpeg instead, a
second in or from the start for shorter clips. Probe for ffmpeg before
downloading, bound every run, and skip videos over 256 MiB.
Migration V32 gives the videos written off so far another try.

Those videos had no server thumbnail because our uploads never sent one.
Every upload path (bulk upload, drained mount writes, conflict copies,
new revisions and folder sync) now attaches a thumbnail rendered from
the local file, kept under the 60 KiB Proton's own clients use. Files
that are not images or videos, or cannot be decoded, upload bare as
before; a .ts file only counts as video with an MPEG-TS sync byte.

ffmpeg is a new optional dependency in the PKGBUILDs.

2026-09-23 20:29:15 +02:00

proton-drive-for-linux

feat(fuse,core): thumbnails for videos and for our own uploads

2026-09-23 20:29:15 +02:00

proton-drive-for-linux-bin

feat(fuse,core): thumbnails for videos and for our own uploads

2026-09-23 20:29:15 +02:00

proton-drive-for-linux-git

feat(fuse,core): thumbnails for videos and for our own uploads

2026-09-23 20:29:15 +02:00

push.sh

chore(packaging): add AUR package sources for source, git, and binary builds

2026-09-21 12:58:13 +02:00

README.md

ci(aur): publish the AUR packages from CI

2026-09-23 11:02:30 +02:00

update.sh

chore(packaging): add AUR package sources for source, git, and binary builds

2026-09-21 12:58:13 +02:00

README.md

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, and LICENSE (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.yml calls 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 to main as chore(aur): update packages to <version>.
On a push to main that changes proton-drive-for-linux-git/, it regenerates that package's .SRCINFO and 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.gz release asset exist.
Run ./update.sh <version> — it rewrites pkgver, resets pkgrel=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 (needs devtools).
Commit here, then publish with ./push.sh (or ./push.sh proton-drive-for-linux-bin for 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.