Amber (@amber@toot.site)
🇳🇱
@abloo I suspect those things need either wayland OR xorg and perhaps you just dont have xorg?
This is something the arch packagers did
Just checked and it's A DAMN BUILD DEPENDANCY
@abloo yea but then why are the other packages claiming they depend on it... iw ouldnt expect an indirect dependency to be reported that way....
Dependancies arent handled very well on arch
Idealy i'd be able to maintain my own repo but i dont have the time or patince to do that
@abloo While arch has been very managable I will admit that I have had some trouble with the dependency rats nest as well, especially when you try to delete a dependency or revert to an older one.
Sadly one of the big issues with a rolling system that aggressively purges older versions and relies heavily on AURs that may need said versions.
Sometimes i miss my Gentoo days just because they would actually maintain quite a few older versions for exactly that reason.
@abloo It has been a few years since I actually used gentoo honestly. But I do recall it being rather trivial to insert your own modified version of a package.
It does rolling updates similar to archlinux (but more so from source than from binary)... if you update often it almost always went flawless for me. That said when i finally left gentoo its because I hadnt updated a system in like 6 months and at that point the dependencies could not longer resolve and it became near impossible to figure out how to update the system. Not sure how common a problem that still is, but it happened once or twice to the point where it took me a week or more to fixand the very last time i just couldnt fix it.... so yea it became the reason I jumped ship.
That said I never once had updates be a problem when i was responsible enough to update regularly. Well not a problem I couldnt fix relatively easily anyway.
This is true. But the problem has always been significantly less in archlinux for me than it has in gentoo. In arch i can always resolve it even in the worst case scenarios.. in gentoo it would happen more often and be much more severe.
Again all this is years in the past and things may have improved since then.
I really dont like the non-rolling distros in my everyday life. But I must admit if its a device I intend to maybe update once a year or something then it is the only sane way to go. I use it often for my hardware projects with single board computers for that reason.
What i really want to try that seems new and unique and not strictly a rolling or non-rolling distro is guix. The whole idea of rolling back updates and doign them as stages feels like the best of both worlds. I say this as someone who knows only very high level vague details about guix.
then all the user software is run with appimage or some local install folder.
non-rolling base image, run whatever rolling workstuff you need.
you have a source file that defines the desired system state and it runs a lot of scripting language to make it happen.
nix also goes further and you configure stuff like users and group memberships and service configs too. it's supposed to create the whole system from a functional config.
nothing really stops you from running ansible/salt to create a new machine from scratch and then flipping over to it (other than the effort and disk space.)
Sounds ok by me, but I'd really have to play with it to get an idea... if its using haskell though that already is a plus. More chances I get to play with haskell the better.
