John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> writes:
> Without --without-threads, guile would not build on SMP systems and even
> the built package would crash on SMP systems.
>
> If disabling threads would break the ABI, we could just rebuild the affected
> reverse dependencies on the builds using the normal binNMU method.
I've checked with upstream, and while they were not certain that
changing the --with-threads setting still breaks the library API, they
thought it probably did, which I believe means we have to assume that it
does (or could in the future), i.e. upstream makes no guarantees that
you can ever change that option without breaking the ABI.
Given that, I think we may have at least these constraints:
- For any guile X.Y version (for a given arch) that's in a stable
distribution (buster, bullseye, etc.) we cannot change the setting
because it would break the contract and could crash existing debian
and non-debian applications linked to the relevant guile-X.Y-libs.
- For any X.Y version (for a given arch) that's only ever been in
unstable/testing, we *could* break the ABI, but I think the bar
should be reasonably high there, and I suspect we may want to
discuss any plan along those lines a bit more broadly before
deciding to pursue it (do we typically allow breaking SONAME
compatibility in testing?), since plenty of people (including me)
use the testing libs for real work. In addition, as you say this
would require rebuilding every reverse dependency.
Of course the best option, if it were feasbile, would be to just figure
out what's wrong and fix it.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
