Repository navigation
Releases
ZLynstall v0.1.0
ZLynstall
Drop a .deb, an .rpm or an AppImage. It just installs.
On any distro. With a menu entry. And a way to remove it again.
What is this?
You found an app you want. The download page hands you a .deb, an .rpm or an .AppImage — and your distro only speaks one of those. On Arch a .deb means an afternoon with debtap. On Fedora a .deb means "no". AppImages work everywhere but sit in ~/Downloads forever, invisible to your app menu.
ZLynstall is one drop zone that does the right thing:
| You drop… | on Arch / EndeavourOS / Manjaro | on Debian / Ubuntu / Mint | on Fedora / RHEL | on openSUSE |
|---|---|---|---|---|
.deb |
rebuilt as a real pacman package and installed |
installed with apt |
rebuilt as an RPM and installed with dnf |
rebuilt as an RPM and installed with zypper |
.rpm |
rebuilt as a real pacman package and installed |
rebuilt as a .deb and installed with apt |
installed with dnf |
installed with zypper |
.AppImage |
moved to ~/Applications, added to your app menu |
same | same | same |
"Rebuilt" means a proper native package: your package manager tracks the files, dependencies get translated to what they're called on your distro, and uninstalling is a normal uninstall. No files sprayed into /opt that nobody remembers.
Everything ZLynstall installs lands in its Library, where you can open it, remove it, repair its shortcuts, give it a desktop icon, or update it by dropping a newer file.
Features
Drop it. Read it. Install it.
Drop a file (or click browse, or right-click it in your file manager → Open with → ZLynstall) and you get a spec sheet before anything happens:
- What it is — name, version, architecture, size, who made it, their website, licence, and the full description on demand. ZLynstall reads all of this without running the file.
- The plan — in one sentence, what will happen on your machine ("Convert to an Arch package and install it with pacman").
- Dependencies, translated —
libgtk-3-0becomesgtk3on Arch,libwebkit2gtk-4.1-0becomeswebkit2gtk-4.1. Anything that can't be translated is shown with a dashed underline and a plain explanation — never hidden, never a silent failure. The install goes ahead without it, because most desktop apps bundle what they need. - Notes you should know about (setup scripts inside the package aren't run when converting; the package was built for another CPU; you already have this version installed…).
- Three switches: add to app menu · desktop shortcut · delete the installer afterwards.
Then press Install (or just hit Enter).
Watch it happen
Every install is drawn as a stage track — Inspect → Translate → Build → Install → Shortcuts — with a little package travelling from node to node, and a plain-language narration underneath ("Translated 2 of 2 dependencies to Arch package names", "Building an Arch package (this is the slow bit)", "Made a menu entry for Hello"). The raw command log is one click away if you're curious.
When it's done, the sheet gets stamped. Soft sounds mark the drop, each finished stage, and the stamp (all optional). Something went wrong? You get a VOID stamp, the real reason, and a hint about what to do. Cancel any time — the running command is stopped and nothing half-done is left behind.
AppImages, done properly
An AppImage is read straight from its embedded filesystem (again, without executing it): its name, version, icon and menu entry come out, and then it's
- moved out of
~/Downloadsinto~/Applications(configurable) and made executable, - given a proper app-menu entry with its real icon,
- optionally a desktop shortcut,
- and registered in the Library so it can be removed cleanly later.
No libfuse2? ZLynstall notices and makes the launcher use the AppImage's extract-and-run mode instead, so it still starts.
The Library
Everything ZLynstall ever installed, in one ledger — .deb, .rpm and AppImage alike:
- Open, Repair shortcuts, Remove on every row. Removing a package uses your package manager; removing an AppImage deletes the file, its icon and its menu entry.
- Search by name, version, package name, author, file path or install date. Filter by kind. Sort newest / oldest / A–Z.
- Click a row for details: description, author, website, licence, architecture, download size, where the file came from, dependencies that couldn't be translated, and the app's version history.
- A right-click menu with everything: open, show in folder, open website, show details, repair shortcuts, add/remove desktop shortcut, set an update folder, copy paths, remove.
- Select mode for bulk actions — repair or remove many apps at once. Removing several packages is one transaction, so it's one password, not one per app.
Updates, without an updater
Most small apps have no auto-updater — you download a new file and wonder what to do with it. ZLynstall turns that file into an update, three ways:
| How | What happens |
|---|---|
| Drop a newer file on ZLynstall | It recognises the app it belongs to (same package, same name, or a matching file name like imagetoolv1.2.0.AppImage), shows "Update · 0.6.0 → 0.7.0" on the sheet, and the button says Update. Same version? It says Reinstall. Older? Downgrade — clearly marked. |
| A global update folder (Settings → Updates) | Point it at a folder. On every start (and on Check now) ZLynstall looks inside, and offers any file that clearly belongs to an installed app and is newer. Nothing is guessed loosely: strangers in that folder are ignored. |
| A per-app update folder (right-click → Set update folder…) | For that one app, any package file in its folder with a newer version is offered — the file name doesn't matter at all. Perfect for apps you build yourself. |
Found updates appear at the top of the Library with Update / Ignore / Update all, and as a red badge on the Library tab. Turn on Install updates automatically and they run by themselves when ZLynstall starts. Every update keeps the app's Library entry and adds the old version to its history.
Shortcuts you can trust
- Packages that ship their own menu entry are left alone; ZLynstall only adds what's missing. Packages without one get a generated entry pointing at the right program (command-line tools get a terminal entry instead of a dead icon).
- Desktop shortcut on install, or later from the right-click menu — and off again just as easily.
- Repair shortcuts re-creates anything that went missing, for AppImages and packages alike.
One password, once
Installing and removing packages needs administrator rights. Instead of a system password prompt for every single action, ZLynstall asks once per session in its own dialog. Your password goes straight to sudo and is never stored — sudo's own credential cache remembers you while the app is open, and it's forgotten the moment you close ZLynstall (or click the UNLOCKED pill in the title bar to lock it again).
Prefer the classic way? Settings → Password → Every time switches to your desktop's normal prompt. If sudo isn't set up for your user, that's what you get automatically. ZLynstall itself never runs as root: only the single package-manager command does.
Settings









