I’d say flatpak isn’t the future because it’s already here and seems to be universally accepted as the cross-distro package manager.

I do like how the Nix package manager handles dependencies, but it’s not suitable for app developers packaging their own apps because of its complexity.

If a better flatpak comes around I’d use it too, but at least for graphical apps I don’t know what it’d have to do to be better. In my opinion, flatpak is a prime example of good enough, but not perfect and I’d be surprised if there was a different tool with the same momentum in 15 years (except snap, but they seem too Ubuntu specific).

This post was posted two times, so you might want to delete one of them.

Bookmarks and GPX export is a great addition. OrganicMaps continues to improve and I find myself using OsmAnd less and less (unless I need specific features).

I’ve now added the date to the title to make it more clear the article is from two months ago. The article is a good read and wasn’t posted on here, so I thought it’s still worth sharing.

Yes, I’ve copied the title from their project.

Proxmox describes itself as an virtualization management platform.

Proxmox Virtual Environment is a complete, open-source server management platform for enterprise virtualization. It tightly integrates the KVM hypervisor and Linux Containers (LXC), software-defined storage and networking functionality, on a single platform

[1] https://www.proxmox.com/en/proxmox-virtual-environment/overview

https://www.qualcomm.com/developer/blog/2024/05/upstreaming-linux-kernel-support-for-the-snapdragon-x-elite

Spotify and Crunchyroll also require DRM, like almost all commercial video sites.

Many flatpaks are not aware of their sandbox and thus have a bad ux.

E.g. flatpak Steam can’t access SteamLibraries at a non-default location, unless the user manually allows the path through flatseal. The same is true for other similar apps which don’t use the file portal.

Issues like this are unexpected for new users and thus it can be argued that flatpak aren’t a good recommendation for new users. I personally disagree because most flatpak work flawlessly and work everywhere independent of a users distro.

It seems the Determinate Nix installer supports Fedora Atomic and SELinux.

On topic:

I really like Nix and home-manager. I’ve mostly switched to NixOS because it’s more convenient for window manager setups than building ublue images imo.

Having to mess with containers for different dev environments and keeping the up to date is imo more annoying than creating a shell.nix

Also being able manage my dorfiles with home-manager and installing software declaratively helps in keeping the system free of clutter.

The source of the determinate nix installer has some mentions of SELinux. E.g. they have an .fc file, but I really don’t know anything about SELinux.

https://github.com/DeterminateSystems/nix-installer/tree/main

Yes, that’s likely the case.

The ahayzen/silverblue-nix guide uses bind mounts from /var/lib/nix to /nix. The latter being created by making / temporarily writeable with chattr +i /.

It seems the Determinate Nix installer supports Fedora Atomic with SELinux enabled.

supporting SELinux and OSTree based distributions without asking users to make compromises

https://github.com/DeterminateSystems/nix-installer

Edit:

disabling SELinux

I hope this is not a serious suggestion?

Since no nix installer supported SELinux at the time, it was the only way to use nix on Fedora Atomic. With a better option available disabling SELinux is a bad idea indeed.

https://gitlab.com/ahayzen/silverblue-nix#using-nix-on-fedora-silverblue

It’s possible to install nix on Fedora Atomic by disabling SELinux and using bind mounts.

Removing nix is mostly done by deleting /nix, and removing some systemd services, as well as deleting some nix-related users or groups (iirc nixblkd)

Because almost all of nix happens in /nix it doesn’t clutter much of the system.

Great to see Unified Push on the list. As well as improved Wayland input method support, whatever that exactly means.

I’m pretty sure microG isn’t installed by default because of how it’d conflict with installing MindTheGapps (Google Apps).

It’s great to see LMFG continuing for a while because its users would have to wipe their device to switch to LineageOS + microG.

That’s awesome. Is it as simple as adding the microG repo to F-Droid and installing from there?

Adding to that, there’re builds of LineageOS with microG preinstalled, which should be relatively similar to CalyxOS.

https://lineage.microg.org/

I personally prefer top level subvolumes (@, @home, @var-log, @var-cache), because it makes it easier to know which system folders are subvolumes and back them up accordingly. They are then mounted at their respective location under /.

E.g… I do snapshots looking at the btrfs filesystem and its top level subvolumes. I’m not doing snapshots going from the mounted root filesystem. I.e. I’d do a snapshot of @home, not a snapshot of /home.

If you want to use backup/snapshot automation tooling, I’d recommend looking at how they expect the subvolumes to be set up. E.g. snapper and timeshift expect a specific layout (which can stil be done manually after OS installation, but why bother).