4 ms·
For Debian it's more than just that the code isn't ready, the debconf guys and the design guys disagree and both consider the merge something that can decide ab
by jeroenhd 5y ago
For Debian it's more than just that the code isn't ready, the debconf guys and the design guys disagree and both consider the merge something that can decide about within the project. And to a certain extend, they're both right, which makes it even worse.
My understanding is that the Debian people tried to get a merged /usr going without consulting the packaging people. The packaging people not only ran into technical issues, they also disagreed with the decision itself. Eventually some patches were made to make it sort of work, but also with a warning that merged /usr is basically unsupported and can lead to breakage (which is technically correct). Then someone else tried to remove the warning because it made the entire project look bad with all those warnings everywhere, and at this point it's just egos and politics from all sides of the argument.
I don't think there are that many actually maintained packages that will break in a merged environment. It's more about the theoretical issue and about principles than anything.
It started out as a technical issue (the invalidation of some core assumptions about the file system in critical packaging infrastructure), but it's so much more than that now. I think the conflict will blow over, but just like people are still advocating for the death of systemd it'll take many years.
I don't think this has caused as much tech debt as it all seems from the aggressive discussions. It's a problem with some packages and some very exotic system configurations (embedded stuff is great at creating those "technically correct and supported but we really shouldn't have encouraged this" edge cases) but for the vast majority of the users and maintainers the whole thing is in the past now.
In the Linux space there are so many things that actually matter, like the 5 second Firefox startup delay caused by Snap and the fact that GTK still lacks a proper thumb grid view after it's been a meme for so many years. This whole issue is kind of a useless thing to put so much energy into.
- throwaway82652 5y ago>that GTK still lacks a proper thumb grid view Qt has the same problem and, at this point, I doubt this will change at all in the next decade. Very few applications actually have any reason to use the default file chooser, and there are basically no developers who have any reason to modify it. If there were, they would have made the changes already sometime in the last "many years". The Snap issue is at least fixable with some caching.