Install a package
Wusel is published as a signed repository through the openSUSE Build Service, so your package manager installs it and keeps it up to date like anything else on the machine. Pick your family below; each is two commands.
If your distribution is not one of the four, skip to A single file, for everything else or build from source: Install from source. Packages is the full table of what is published where.
Installing does not switch Wusel on. Do Mount at login afterwards — or follow a tutorial, which walks the whole way: on GNOME, on another desktop or on a server.
Fedora
sudo dnf config-manager addrepo --from-repofile=https://download.opensuse.org/repositories/home:/cdhermann:/wusel/Fedora_44/home:cdhermann:wusel.repo
sudo dnf install wusel
The repository is built for Fedora 44. dnf imports the signing key on first
install and asks you to confirm its fingerprint.
openSUSE Tumbleweed
sudo zypper addrepo https://download.opensuse.org/repositories/home:/cdhermann:/wusel/openSUSE_Tumbleweed/home:cdhermann:wusel.repo
sudo zypper refresh
sudo zypper install wusel
Debian 13
echo 'deb http://download.opensuse.org/repositories/home:/cdhermann:/wusel/Debian_13/ /' \
| sudo tee /etc/apt/sources.list.d/home:cdhermann:wusel.list
curl -fsSL https://download.opensuse.org/repositories/home:cdhermann:wusel/Debian_13/Release.key \
| gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_cdhermann_wusel.gpg > /dev/null
sudo apt update
sudo apt install wusel
Ubuntu 26.04
The same, against the Ubuntu repository:
echo 'deb http://download.opensuse.org/repositories/home:/cdhermann:/wusel/xUbuntu_26.04/ /' \
| sudo tee /etc/apt/sources.list.d/home:cdhermann:wusel.list
curl -fsSL https://download.opensuse.org/repositories/home:cdhermann:wusel/xUbuntu_26.04/Release.key \
| gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_cdhermann_wusel.gpg > /dev/null
sudo apt update
sudo apt install wusel
Arch Linux
Not on the AUR yet, but the PKGBUILD is in the repository and builds the way
any AUR package does — there is nothing AUR-specific about running it from a
local checkout:
git clone https://github.com/itbh-at/wusel.git
cd wusel/packaging/aur
makepkg -si
-s installs the build dependencies through pacman first; -i installs the
result. Updating means pulling and running it again.
A single file, for everything else
Every release also attaches one RPM and one .deb per architecture to its
GitHub Release. These are
unsigned, and nothing updates them for you — fetch the next release the same
way. Use them when you cannot add a repository, or when your distribution is
none of the four above and is close enough to Fedora 44 or Debian 13 to run
one.
sudo dnf install ./wusel-*.rpm # RPM-based
sudo apt install ./wusel_*.deb # Debian-based
Use apt, not dpkg -i. apt resolves the dependencies; dpkg only reports
that they are missing.
Staying up to date
This is the point of the repository, and it needs no further setup: Wusel is now an ordinary package on the machine, so whatever you already run to update the system picks up each new release.
| Distribution | Updates arrive with |
|---|---|
Fedora |
|
openSUSE Tumbleweed |
|
Debian, Ubuntu |
|
Arch |
Nothing automatic. |
A single file from a GitHub Release |
Nothing. Download the next one and install it over the top. |
A new version does not restart your mount. After an update, either log out and back in, or:
systemctl --user restart wusel@default
The Nautilus extension and the search provider are loaded at session start, so a full re-login is what picks those up — see below.
Then log out and back in
The Nautilus extension and the GNOME Shell search provider are loaded by their host processes when a session starts, so they are not picked up by the running one. Log out and back in once.
Faster, if you would rather not: restart Nautilus with nautilus -q (it
relaunches on next use), and restart GNOME Shell — on X11 press kbd:[Alt+F2],
type r, press kbd:[Enter]; on Wayland only a re-login does it. A full re-login
always works.
What is installed, and what is not
The one required dependency is fuse3. The GNOME pieces are suggested, so
neither package manager installs them by default: on a server or a KDE machine
you get the mount and about five packages rather than a desktop stack. What is
then missing is the sidebar entry, the emblems and the Shell search — not the
filesystem. See Platform support.