540
Monster (lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
[-] Chewy7324@discuss.tchncs.de 40 points 1 year ago

Yes, but each package manager has it's (dis-)advantages. It's great to have flatpak and docker to be able to run software on almost all distros, but the OS still needs a way to update.

Almost all immutable distros use multiple package manager.

  • Fedora Silverblue: rpm-ostree + flatpak (+ toolbox)
  • OpenSUSE MicroOS: zypper with snapshots (transactional-update) + flatpak (+ distrobox)
  • NixOS is unique since it only uses the Nix package manager
  • immutable Ubuntu will probably only use snap for OS + apps.

All those OS support distrobox and docker additionally.

[-] monk@lemmy.unboiled.info 18 points 1 year ago

NixOS is unique because it uses the only potent package manager (if we don't count that one reimplementation of Nix). Calling the others "package managers" becomes mostly a courtesy when NixOS enters the picture.

lalala with FS-level snapshots + flatpak + distrobox + a kitchen sink

look_what_they_need_to_mimic_the_fraction_of_our_power.png

I don't consider myself a dumb person but I couldn't figure out nix when last I decided to play with it. Theoretically it seems super interesting to me, but I really just can't dedicate the time again now to learn that esoteric syntax.

[-] Chewy7324@discuss.tchncs.de 17 points 1 year ago

The docs for NixOS aren't good. Much knowledge is on many blogs but who knows them all?

Having the OS defined declaratively is great but I also dislike the Nix language.

Once it's setup NixOS is great. Sharing configs with PC and laptop is awesome. Rollbacks are baked in.

Going off the https://github.com/Misterio77/nix-starter-configs helped me gettung started.

[-] silicon_reverie@lemmy.world 9 points 1 year ago* (last edited 1 year ago)

I absolutely loved NixOS on paper, and it's undoubtedly the best way to combat updates that break my dependency trees, but I still found myself spending a majority of my time attempting to hard-code various app configuration files into my convoluted configuration.nix with its esoteric syntax rather than actually using my computer. Am I missing something, or does a good install script covering my favorite packages and a git bare repo storing my dot-files get me 90% of the way there without the hassle of bending my whole OS around a single nix config monstrosity?

[-] Chewy7324@discuss.tchncs.de 2 points 1 year ago

Agreed, I'm also considering switching to an install script + btrfs snapshots. It worked quite well a few years ago, altough it doesn't solve configuration drift.

[-] monk@lemmy.unboiled.info 1 points 1 year ago

Only if you reinstall every time you change the configuration. And never need to do anything remotely fancy.

[-] mac@infosec.pub 1 points 9 months ago

I found zero to nix to be a good tutorial

[-] monk@lemmy.unboiled.info 1 points 1 year ago

The syntax is just the outer layer, the whole concept inside it is alien. It's like a smartphone for a person who's only seen books.

[-] pimeys@lemmy.nauk.io 2 points 1 year ago

You can use at least appimage with NixOS...

[-] monk@lemmy.unboiled.info 12 points 1 year ago

You cah also tow a Tesla with a couple of horses

[-] null@slrpnk.net 3 points 1 year ago
[-] merthyr1831@lemmy.world 1 points 1 year ago

all the more reason to sunlight these old packaging formats and move to universal solutions like flatpak and nix

this post was submitted on 03 Nov 2023
540 points (93.8% liked)

linuxmemes

21197 readers
57 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS