Originally posted by intellivision
View Post
It was clear from the beginning, that when the original authors had abandoned CK, that CK was on essential life-support only. The problem being, that CK allegedly is a rather nasty codepile that was never very well documented.
There have been numerous "warnings" about this for years, also on the Debian developer lists, but those few that allegedly tried to look into CK, found it difficult and beyond their ability to maintain. Well, no wonder. That the CK code base is byzantine has been stated by anyone involved in it. Don't blame the unfortunate temporary maintainers that they won't bother holding hands for anybody trying to maintain a difficult code base they themselves left a year ago, they may have other things to do in their life. And they are not withholding any documentation; there never was any.
So now CK have been bit rotting for +1? years. Don't blame the systemd guys for actually develop an well documented functional alternative to CK. If they can, why can't the non-linux guys?
The bit rotting is now so bad, that upstreams DE's have problems supporting it, and upstream DE's certainly aren't getting help for this from anybody.
The right solution isn't ranting against Poettering, freedesktop.org or anybody else, but to get of the couch and start coding.
Leave a comment: