Coming up, any day now, is your new 66 package.
obcore-testing/66 0.2.4.0-5 (base s6-suite)
small tools built around s6 and s6-rc programs
obcore/66 0.2.3.2-1 (base s6-suite)
small tools built around s6 and s6-rc programsNo .zstd packaging here, just good old xz, despite of the 0,0094 second decompression advantage. 🙂
Ok, 0.2.4 over 0.2.3… brings yet one more tool to you. Still, the package (66) is only a fraction of systemd, but it has more “features”. That database of trees and services you have created, after a major reorganization of 66 and its service file definitions and syntax do not have to be destroyed and recreated, not for the root and not for the user. Simply run 66-update as root and as user after each upgrade to ensure perfect transitioning to the upgraded software. 66-update -v4 for maximum verbosity.
The next step in development will be a more automated backup and restore of your trees and services structure.
In the past 9 months 66 evolved quite a bit and after each major evolutionary step the safest way to upgrade was to destroy old trees (delete them) and recreate them and populate them with services. Not any more. But that is not all. 66-update doesn’t mean it is a one way procedure, Say you found out something is wrong, you located the bug of the century, something wrong with 66, and you want to downgrade back to the previous edition of 66. You downgrade the package and run 66-update again.
PS Now, if someone who is not banned from r/linux or r/archlinux could try and crosspost this important announcement there, to see if you can do this for a banned user like me, it would be nice to know, that I can still piss them off with my existence.