On Thu, 07 Sep 2023 21:28:15 +0100, Luca Boccassi wrote: > Yes, that is fine by me, as explained in later replies my main > intention is to fix the issue that some wording is being used to > reintroduce things that should not be reintroduced
If I understand you correctly, "Reintroduc[ing] things that should not be reintroduced" means not acting on bug reports where someone says "Please change #!/usr/bin/sh back to #!/bin/sh". If I'm understanding the technical question correctly, "#!/bin/sh" works for both merged-/usr and split-/usr, while "#!/usr/bin/sh" works only for merged-/usr and breaks for split-/usr. Now, how to handle this situation? In my naïve point of view and a bit late at night I see two options for maintainers. They can say … 1) "Well, right, *sigh*, ok, let's take the five minutes to change this back to "#!/bin/sh", and everyone's happy." … or … 2) "No way, we are usr-merge, resistence is futile, go <expletive deleted> yourself, "#!/usr/bin/sh" is the default, bad luck for you !!!!111" I'm a bit sad that many discussions in Debian (like this one) turn into the "my way or the highway" lane, and I'd rather see a way of cooperation which gives more leeway to others and take small extra steps to accomodate minorities, when it doesn't have any actual cost. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `-
signature.asc
Description: Digital Signature
