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.
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
locally; the AUR itself is a roadmap item.
Single files, per release
Every v* tag also attaches one package 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
Only one dependency is stated outright:
fuse3-
for the setuid
fusermount3helper that an unprivileged mount needs.
The shared libraries the binary and the Nautilus extension link against are resolved automatically as soname dependencies, so they are not listed by name.
The GNOME pieces — nautilus and gnome-shell — are suggested, not required
and not recommended. Neither dnf nor apt installs a suggestion by default, so
a server or a KDE machine gets the mount and about five packages, not a desktop
stack. What such a machine loses is the sidebar entry, the emblems and the Shell
search; the mount itself is unaffected. The search provider in particular links
no GNOME library at all — it is the wusel binary answering D-Bus, which the
Shell activates on demand.
Before 0.2.2 these were Recommends, which both package managers do
install by default.
|
What a package installs
| Path | What it is |
|---|---|
|
The binary — daemon and CLI in one. |
|
The systemd user service template. One instance per account:
|
|
The native Nautilus extension: per-file emblems and the Make Available Offline / Free Up Space menu. 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. |
|
The application icon, used by the sidebar entry and the search results. |
|
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 |
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.