* David H. Gutteridge <david%gutteridge.ca@localhost> [2019-03-01 23:21 -0500]:
On Mon, 25 Feb 2019, at 19:53:57 -0500, David J. Weller-Fahy wrote:It might, but I'm not sure of the proper location for such documentation.The bootstrap directory has various README.OS files in it, those typically document considerations like this. (Though there's also separate documentation found on the NetBSD Wiki too: https://wiki.netbsd.org/pkgsrc/how_to_use_pkgsrc_on_linux/) Regardless of what's done for this particular item, there might be ways to draw more attention to this documentation.
Good point: I hadn't looked at those! However ...
I'm not one of the main pkgsrc pythonistas, so we'd need some consensus from them on this. A PR is probably a good idea for this.
After filing a PR [1], it was closed as a duplicate because someone had already noticed the issue on Python 3.7 (PR [2]). While my fix is good for short term, I have a feeling they're working on a larger fix. [1]: https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=54056 [2]: https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53673
I don't feel it's necessary to confine the check to a particular distro (or family of them). For any that use glibc, it's simply a question of when they integrate the version that's made this change. (And how, I suppose, as they might handle it differently than Fedora did. I saw in one of the Python bug reports there seemed to be uncertainty about this.)
Concur.
Thanks for the work you've done on this,
You're welcome, and thanks! I guess we'll have to wait to see what the consensus is for the global fix. Regards, -dave
Attachment:
signature.asc
Description: PGP signature