News for hackers. Stuff that matters.
Re:The golden rule of software distributions by Mathnerd314 on Monday May 09, 2022 @05:55PM (#31320311)
A rolling release is not a "pre release" but rather a continuous succession of releases, one for every package update. To the extent the rolling release has no broken packages it is completely globally coherent. And I don't think a failing package is necessarily a failure in coherence either - it just means the blessed version is broken. Incoherence is when you have A depending on C-1.0 and B depending on C-2.0 and the two versions of C not simultaneously installable (local coherence of C) - it is only the complex constraint-solving package managers that would be able to function with such a dependency tree. Such a situation is unlikely to occur in a rolling release - it is more likely to have two C package C1-1.0 and C2-2.0 which do not conflict.
Re:The golden rule of software distributions by froh on Tuesday May 10, 2022 @12:55AM (#31323602)
Good point. We have to distinguish if it has been built coherently or if it actually works. I was obviously thinking of the latter, it's the one that's uaefzl. In that sense a rolling release may _claim_ coherence, buld coherence that is, while it still is locally incoherent (some packages don't work).
Re:The golden rule of software distributions by froh on Tuesday May 10, 2022 @03:23PM (#31331435)
Oh. I have no idea how autocorrect transmogrified "the one that counts" into "the one that uaefzl".