I am an avid #foss and #linux enthuist. Like a large amount of people in the foss community, I have #autism and #adhd.

I tend to post about a little bit of everything.

I run #NixOS on my Laptop and #opensuse #leap on my #server PC which is running the instance that I’m on.

#fedi22

  • 0 Posts
  • 39 Comments
Joined 2 years ago
cake
Cake day: December 22nd, 2022

help-circle


















  • @lambda @BeigeAgenda

    Imo a better alternative to flatpak is the nix package manager, but as I said to the other guy this’ll most likely end up a VHS/betamax situation.

    Both things are trying to solve dependency hell in different ways. Flatpak just builds and runs everything in a container, where as nix sets up virtual environments and builds things in isolation with per package dependency trees in an effort to make builds entirely reproducible (to the point that no matter what system you compile on, you will get the same hash).

    Edit: as the other guy said, just use your systems package manager unless it doesn’t exist in the repo and you can’t be bothered to package it yourself. It’s the standard recommended method.


  • @orcrist @lambda

    There definitely is a problem that flatpak is trying to solve. That problem is dependency hell.

    This most often (or rather most famously) occurs with python packaging. Sometimes you can have one package that requires a version that is incompatible with another version that another package requires. That’s why people use python venv these days (or just use pipx).

    IMO a better way of solving this is with nix. With nix, it doesn’t require a container, it just builds in isolation.

    Thing is, this will probably end up a VHS vs Beta Max.