• 5 Posts
  • 512 Comments
Joined 11 months ago
cake
Cake day: August 10th, 2023

help-circle






  • Is that so? From the issue I read there was no way around it because the two images are fundamentally incompatible once you layer that package, you had to remove the layered package, it seemed from the discussion that they might have “fixed” the base image at some point as a pull request was opened on Pagure. I waited a bit for it to go upstream, but nothing happened for a long time and just went thorugh with the manual intervention, and actually, now that I check it again, the maintainer siosm commented that they can’t accept the PR



  • Love the irony, but this is painting a little too good a picture

    Every update is just… meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking

    Most times yes, but major updates usually cause some trouble, like from 39 to 40, you couldn’t do it without uninstalling the codecs for Firefox. Firefox that is installed by default as an RPM, because the Flatpak Firefox doesn’t yet have 100% compatibility with all the features that work with the RPM, so as a user you’re pretty much led to get yourself stuck in this hole, not too difficult to fix in the end, but still a pain to find out and fix.

    Everything else is 100% true! And I think it will be always hard to beat as an implementation of immutability (second place only to NixOS imo), A/B partitioning doesn’t hold a candle to OSTree








  • Both features are important IMO, reproducibility is for being able to define certain aspects of your machine in a way that you can nuke it and, as long as you have its configuration (declarative for Nix, other implementations might have it as imperative), bring it back just how it was set up, without differences or breakages; while immutability is for being always confident that whatever* you do to your machine, you won’t be able to break it because the root, which holds the functioning core of your system, can’t be messed around with, NixOS has both I believe.

    *not really “whatever”, because there are still some ways to break, but you have to be very deliberate in doing it (think rm -rf /*), but in normal operation you won’t just somehow install something or upgrade your packages and be left with an unusable system




  • uninformed comment

    That’s fine in and of itself, but, personally, I could never bring myself to use a forge which isn’t fully featured and easy to use.

    (rant)

    Sourcehut is just so counterintuitive to me and I shrug every time I see a project actually using it, I feel like many wouldn’t even consider making contributions unless they were very motivated. To the average person, it just looks like an unwelcoming experience, especially for the email centric focus, like, why should I switch to another application just to open an issue? At least integrate it with the the web UI, like idk, make it a specialized email client for the platform, so I don’t have to juggle multiple things.


    Don’t get me wrong tho, it’s the closest we have to the bare git workflow of the “before times” with a bit more accessibility on top, it’s not bad, but in a way these new web forges have spoiled us devs into relying on cohesive web services which happen to have vendor lock-in, but that can change and it is slowly doing so


    edit: deleted for inaccurate info, don’t consider my dumb rant O.o

    I found it unfamiliar in the few times I saw it, but maybe it’s worth giving a try