pepepper/fluxer
1
0
Fork 0
mirror of https://github.com/fluxerapp/fluxer synced 2026-10-07 19:22:14 +09:00
Code Issues Packages Projects Releases Wiki Activity

docs(downloads): one pacman repository holds both channels (#2855)

Browse Source
This commit is contained in:
Hampus
2026-09-20 02:50:08 +02:00
committed by GitHub
parent 5d85e88532
commit 86043212f2
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fluxer_docs/src/content/docs/downloads/linux-repositories.md
+6 -2
View File
@@ -4,7 +4,7 @@ title: Linux repositories
description: The apt, dnf, pacman and Flatpak repositories Fluxer publishes, and how a client adds them. description: The apt, dnf, pacman and Flatpak repositories Fluxer publishes, and how a client adds them.
--- ---
Fluxer publishes four Linux repositories. The apt, dnf and pacman entrypoints each subscribe to one channel, so the file you install decides whether you track stable or canary. The package name follows from that, `fluxer` for stable and `fluxer-canary` for canary. Flatpak is the exception: one remote serves both, and the application id selects the channel. Fluxer publishes four Linux repositories. In every one the package is `fluxer` for stable and `fluxer-canary` for canary. The apt and dnf entrypoints each subscribe to one channel, so the file you install decides which of the two you track. pacman and Flatpak work the other way. One repository serves both channels, and the package name or application id selects it.
## apt ## apt
@@ -39,6 +39,8 @@ The package depends on `libXScrnSaver`, which the EL base repositories do not sh
## pacman ## pacman
One repository named `fluxer` holds both channels.
``` ```
sudo tee -a /etc/pacman.conf >/dev/null <<'REPO' sudo tee -a /etc/pacman.conf >/dev/null <<'REPO'
@@ -49,7 +51,9 @@ REPO
sudo pacman -Syu --noconfirm fluxer sudo pacman -Syu --noconfirm fluxer
``` ```
Write `$repo` and `$arch` literally. Both are pacman variables, not shell ones, which is why the heredoc above is quoted. `$repo` expands to the section name, so the same line works for `fluxer` and `fluxer-canary`. Install `fluxer-canary` instead for the canary channel. Both come from this one repository and install alongside each other.
Write `$repo` and `$arch` literally. Both are pacman variables, not shell ones, which is why the heredoc above is quoted. `$repo` expands to the section name, so the `Server` line needs no editing.
A pacman sync database records one version per package name, so only the current release is installable by name. An older build is still served, and `curl` followed by `pacman -U ./<file>` installs it. A pacman sync database records one version per package name, so only the current release is installable by name. An older build is still served, and `curl` followed by `pacman -U ./<file>` installs it.