One way or another, if you want to run an application you are gonna need its dependencies (the key is the name)… they may be bundled into an appimage or come as part of flatpak ruintime, or be confined inside a container, or live in the nix store, but they will “bloat” your system anyway.

Learn how to cleanup your system (ie. uninstall all packages that are not needed by others that have been requested explicitly) and live a happy life. Only bother with other solutions if the software (or version) you need isn’t available for your distro.

Because podman :)

The main difference is probably that I have a desktop PC rather than a laptop (plus, a few old hard disks lying around).

I think I’ll keep the local replica even when I’m finished reorganizing the library: the local copy doubles as a backup and I must say I am enjoying the faster access times.

I also read that drives should not be spun down and up too often, but I think it only matters if you do that hundreds of times a day?

Anyway, the reason I spin down my drives is to save electricity, and… more for the principle than for the electric bill (it’s only 2 drives).

I am amazed at the achievement, and even more amazed at how much people can cheer at anything like madmen.

Never heard of it… OMG that must be the worst name for a backup solution! :D

It reeks of abandoned software (last release is 0.50 from 2018), but there is recent activity in git, so… IDK

Yes, Syncthing does watch for file changes… that’s why I am so puzzled that it also does full rescans :)

Maybe they do that to catch changes that may have been made while syncthing was not running… it may make sense on mobies, where the OS like to kill processes willy-nilly, but IMHO not on a “real” computer

That’s the thing you want to build (a single project may generate multiple executables - eg. a server and a client) so it won’t help in this case but… I must say, I am impressed and really grateful that you went and looked that up for me! Thanks, mate!

cabal2nix doesn’t care about any source-repository-package in cabal.project (I think it doesn’t even read that file?).

In my case, it generated a project that depended on the aeon from nixpkgs (which IIUC in turn comes from hackage) rather than the forked version.

I agree: flakes are great for development (and not only)!

Unfortunately I still need to build that third party project from source :)
Maybe I should look into disregarding the whole haskellPackages infrastructure and just build with cabal via a shell script… IDK if that would be accepted in nixpkgs though :/