Packages
Every v* tag builds packages for x86_64 and aarch64 and attaches them to a
GitHub Release. To actually
install one, see Install a package.
Wusel comes as two packages:
wusel-
the mount — the binary, the systemd user service, and the desktop integration the binary provides itself over D-Bus: notifications, the Files sidebar entry and the GNOME Shell search provider.
wusel-nautilus-
the GNOME Files (Nautilus) integration — per-file emblems and the Wusel context menu. It requires
wuselof exactly the same version.
Integration with a file manager is always its own package, named
wusel-<file manager>, so a machine installs only the file-manager libraries
it actually uses.
The repository
Wusel is published as a signed repository through the openSUSE Build Service, at
https://download.opensuse.org/repositories/home:/cdhermann:/wusel/. Adding it
is the normal way to install; see
Install a package.
| Distribution | Repository | Architectures |
|---|---|---|
Fedora 44 |
|
|
openSUSE Tumbleweed |
|
|
Debian 13 (trixie) |
|
|
Ubuntu 26.04 |
|
|
The architectures are spelled the way each ecosystem spells them: an RPM
repository says x86_64 and aarch64, a Debian one says amd64 and arm64
for the same two machines.
The RPM repositories carry gpgcheck=1 and a signing key at
<repository>/repodata/repomd.xml.key; the Debian ones a Release.key. Your
package manager verifies every package against it, and updates arrive with the
rest of the system.
Arch is not in the build service. The PKGBUILD under packaging/aur/ builds
on your machine, from the release tarball of the version in its pkgver —
currently 0.2.2, behind the other packages — not from the checkout it sits in.
The AUR itself is a roadmap item.
Single files, per release
Every v* tag also attaches both packages, per format and architecture, to its
GitHub Release. These exist
for machines that cannot add a repository, and for distributions the build
service does not target.
| File | Format | Built for |
|---|---|---|
|
RPM |
Fedora 44. The |
|
Debian package |
Debian 13 (trixie), and Ubuntu releases close enough to it. A |
These are unsigned, and nothing updates them for you. Prefer the repository wherever you can use it. If neither fits, build from source: Install from source.
Dependencies
The mount needs no desktop. wusel states one dependency outright:
fuse3-
for the setuid
fusermount3helper that an unprivileged mount needs.
The binary links only libc, libm and libgcc_s. Notifications, the sidebar entry
and the search provider are the wusel binary speaking D-Bus, which it does
without any library — the Shell activates the search provider on demand. So
wusel brings fuse3 and nothing else: about four packages on a minimal
Fedora or Debian.
wusel-nautilus requires wusel of the same version and the libraries the
extension links against — the Nautilus extension library and GLib — resolved
automatically as soname dependencies. It brings only what Nautilus itself uses:
two more packages on Fedora, nine more on a minimal Debian, none of them GTK.
The extension is compiled against GTK but does not link it; the few clipboard
calls it makes resolve inside Nautilus, which has GTK loaded.
wusel suggests wusel-nautilus and gnome-shell — not required and not
recommended (on Arch, optional dependencies). Neither dnf nor apt installs
a suggestion by default, so a server or a KDE machine gets the mount and no
desktop stack. What such a machine loses is the emblems and the context menu;
the mount itself is unaffected.
The RPM subpackage also declares Supplements: (wusel and nautilus): where
Nautilus is installed, dnf and zypper install wusel-nautilus along with
wusel on their own. Debian and Ubuntu have no such mechanism, so there
wusel-nautilus is installed by name.
Before 0.2.2 the GNOME pieces were Recommends, which both package
managers do install by default.
|
What the packages install
wusel
| Path | What it is |
|---|---|
|
The binary — daemon and CLI in one. |
|
The systemd user service template. One instance per account:
|
|
The full-colour application icon — the app-grid / launcher entry and the search results. |
|
The monochrome variant GTK re-tints to the theme foreground. The file-manager sidebar entry uses it, so it stays legible in Dark Mode. |
|
The launcher entry the search provider resolves its identity from. |
|
D-Bus activation for the search provider — this is what lets GNOME Shell start it on demand, with nothing running in the background. |
|
The search provider’s registration with GNOME Shell. |
|
The Files sidebar registration for the default account. Named accounts
register their own with |
|
Licence and README (RPM and Arch). The |
wusel-nautilus
| Path | What it is |
|---|---|
|
The native Nautilus extension: per-file emblems and a Wusel context submenu — Make Available Offline / Stop Keeping Offline, Update Now, Open in Nextcloud, Open Folder in Nextcloud, Copy Internal Link. Tied to the Nautilus major version, so it is built against the target distribution’s own Nautilus. |
|
The emblem icons the extension draws. See File states. |
|
Licence (Arch). The |
Removing wusel — not upgrading it — also deletes the sidebar
registrations wusel desktop install-provider wrote for named accounts, which
the package never owned. All three formats do this.
Nothing is installed into a home directory. Everything Wusel writes per user is created at run time; see Files and directories.
Building them yourself
The recipes live in the repository under packaging/rpm/, packaging/deb/ and
packaging/aur/, each with its own README.md. See
Build a package.