Linux installs fast. Then you spend the next hour doing the same boring ritual: browser, codecs, media tools, chat apps, dev tools, fonts, utilities… all via tabs, notes, and half-forgotten package names.
So I built LinuxMate: a free, open-source helper that generates a clean “get me productive” install script from a checklist. Basically Ninite, but for Linux, and without the “sign in to continue existing” vibes.
- Pick apps/tools
- Choose your distro / package manager
- Get a reproducible script
- Run it and move on with your life
Live demo: https://www.allroundwebsite.com/linuxmate/ Repo: https://github.com/Henkster72/LinuxMate Blog (my reasoning / background): https://www.allroundwebsite.com/blog/bye-windows-hello-linux-and-linuxmate/
If you’ve got strong opinions (the useful kind): distro support, package picks, safer defaults, or edge cases, I’m collecting feedback.
I simply dump the installed packages into a text file and then use that on the next install.
Pseudo terminal commands:
packagemanager list installed -nodeps >> myfacorites.txt packagemanager install `cat myfacorites.txt`True. But someones taste… there are more ways to get to Rome 😉
Linux MATE desktop is pretty established and I think has a similar audience. Pretty confusing name choice… “want to install mate on linux? Try linuxmate (no relation)”
BTW are those actually your reasonings on the blog as you say? It reads very LLMy.
It is indeed with the help of llm. But reasoning is still solid and very curated.
want to install mate on linux, mate? Try linuxmate (no relation)
FTFY
Haha yes, but this time without the space
Basically Ninite for Linux, I see the vision!
Sugestion: Hide the ‘AUR helper’ if Arch isn’t selected.
Done
Selecting Flaptpak, it shows ~95% of the options are “not available for your distro”…
Which flap 😜
I get that you’re aiming this at a user base of new folks and all, but I’m super confused to see Nix on there.
This is kind of…Nix’s entire identity, no?
One could also make the argument that this supercedes bootstrap tools that each distro has. Kickstart for example.
I would maybe focus on making helper scripts that do specific things for groups of users, like installing all the steam-* packages for Steam installs and not just steam itself since this is pretty opinionated on how you’re choosing to install things re: native package manager vs Flatpak and such.
looking into it!
Funny, I just saw the video of Mental Outlaw talking about TuxMate. How do you think your project compares to this?
This LinuxMate has more packages, more distros and it is faster
This looks good. I’m an idiot and I use mint. Could I still use this on mint if I just select Ubuntu?
Added linux mint… but yeah same as Ubuntu
For the most part, yeah
It looks great but I don’t like it.
You decide that firefox gets installed via apt and not flatpak. Why?
This aims at someone who already has a system and wants to have some reproducible thing for a new system.
Back the fuck up and restore from backup.
This also includes take asnapshot of flatpak apps and simply reinstall all of them on the new system.
Yes, there is a lot of improvement to automatically do all this. But not with another solution. Just use dotfiles. Dotfiles and a cloud sync thing.
Sure! But hey… some people like it differently
@illusionist @henkster Firefox from apt and firefox from flatpak are not equivalent. The former goes through an extra process to remove non-free components.
true so how to make it better?
Neither do native and flatpak vscode work the same way. It’s about that OP decides it, not the user.
@illusionist At least with the demo that I’m looking at with the script to download, it gives both flatpak AND apt install commands, giving the user a choice. Maybe I’m looking at the wrong thing though?
Your right. The rest of the comment still holds. Backup and restore.
Edit: I have to sanitise the final script and remove all the wrong commands afterwards 🤔
what do you mean?
Backup apps with e.g. this https://www.nixtutor.com/linux/keep-a-backup-of-installed-packages/ and this https://itsfoss.com/back-up-restore-flatpak-apps/ and borg/pika/deja dup/kopia for files. Let’s add appimages, snaps and brew and containers/distrobox.
The only thing that is missing is an all in one solution that puts everything together. And a cloud where you can restore it.
I like it! Bookmarking for future reference, since it seems helpful. Only thing I’d noticed that I think would be a good addition: Some kind of XMPP client, at least one of them. I use Dino on desktop primarily (fairly modern UI, has the core features in, but is made for GNOME so looks a bit funky on anything else), but Kaidan, Pidgin, and a few others exist.
Done
Nice. But just a note nixOS and MicroOS both have config files so you can replicate an exact install. OpenSUSE has autoyast so you can define a system and port that to your next install.
true. but autoyast is not everyones cup of tea
Do you mean because of having to build your system first then write out the config via autoyast? To then use the config next time you install?
If that is the an issue then MicroOS is probably a better option for someone, they have a config builder to insert, so at first boot the system installs itself.
Nice. But just a note nixOS and MicroOS both have config files so you can replicate an exact install. OpenSUSE has autoyast so you can define a system and port that to your next install.
henkster OPEnglish
true. but autoyast is not everyones cup of tea
BCsven @lemmy.ca English
Do you mean because of having to build your system first then write out the config via autoyast? To then use the config next time you install?
If that is the an issue then MicroOS is probably a better option for someone, they have a config builder to insert, so at first boot the system installs itself.
True, and you’re 100% right that NixOS, MicroOS (Ignition), and AutoYaST can reproduce an install very cleanly.
LinuxMate isn’t trying to replace declarative provisioning though. It’s aimed at the everyday desktop distros and the “first hour after install” problem: getting your common apps onto multiple machines fast, in a way that’s shareable and distro agnostic.
For people already living in NixOS configs or MicroOS Ignition, you’re probably set. For everyone else (Mint, Ubuntu, Fedora, Arch, mixed LAN machines), a simple app picker that outputs one batched script plus URL presets is a nice on ramp.
Also good note on Fuel Ignition. Quick safety tip for readers: Ignition uses passwordHash and it’s best to use SSH keys or generate the hash locally rather than typing a real password into any website.
