Thread of 3 posts
jump to replies
i wasn't expecting gnome-session to drop the legacy service stuff now (though i had expected them to drop it much earlier, given it's been pretty much unused in everything except gdm and non-systemd distros for a long time) but in the end it doesn't really change that much
chimera will stick with gnome-session 48 for this release because it's going to be tricky to deal with things (if i was given an earlier notice i would've probably prepared things ahead of time...) but making things properly supervised with the service manager has really been the plan since forever so all this does is push it along a little, since i no longer have the option to delay it further
all the complaints about it are kinda stupid, the legacy handling code is kinda terrible and janky, doing away with it is a good thing overall and if your non-systemd service manager is worth anything at all, you *can* replicate the same (better) approach
and if your service manager can't, well, noone has any obligation to accommodate your boomerware
ok that's my designated techpost of the week, i really want to keep them to a minimum~
also, i *will* be doing all the work necessary to deal with this stuff (i have a lot of plans to make things better for everyone in the long run, but for now i'll stick with what's strictly necessary to react to the upstream changes) so in not too long there should at very least be patches that should be adaptable to other systems easily enough (at least if your own system can provide some basic necessities)
it may seem scary right now but i never considered the status quo sustainable so hopefully this can actually result in something that will be more robust and better for all~
3 visible replies; 1 more reply hidden or not public
back to top
@q66 tysm for everything youre doing ❤️
@q66 am I free to use "boomerware" because that's one hell of an amazing word.
@thomholwerda i'm 99.9% sure i have not invented it