This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yossarian
Recipients Lukas.Vacek, christian.heimes, yossarian
Date 2021-04-03.17:06:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20210403170644.eenelce4fn3ng5iv@janus>
In-reply-to <1617468334.52.0.202587490721.issue38794@roundup.psfhosted.org>
Content
I don't think this is a productive or polite response.

If you read the issue linked, you'll note that the other flag added
(--with-openssl-rpath) is in furtherance of any *already* supported linking
scenario (dynamic, with a non-system-default OpenSSL). The proposed change
here is for an *new* linking scenario, i.e. statically linking OpenSSL.

I don't blame the maintainers for not wanting to add another build configuration
to their plate, especially for something like OpenSSL. It's up to us as end
users to make those accommodations on our own, knowing that what we're
doing isn't tested or directly supported. The resolution above is, in my
book, the ideal one.

Best,
William

On Sat, Apr 03, 2021 at 04:45:34PM +0000, Lukas Vacek wrote:
>
> Lukas Vacek <lucas.vacek@gmail.com> added the comment:
>
> For the record, this would have been solved more than a year ago already.
>
> When this change was proposed more than a year ago it was rejected with "There is no need to add more configure flags to build Python with a custom OpenSSL installation. " yet now it's ok to add a new option --with-openssl-rpath https://bugs.python.org/issue43466 ?
>
> And the first comment there, from python core dev nonetheless, is suggesting static linking as well. Emm... this would have been solved year and half ago. I would be happy to completely drop my proposed (and approved on gihub) changes and implement it in a different way.
>
> The maintainer's attitude as demonstrated here can be really harmful in open-source projects (many of us still remember eglibc fork back in the day) but fortunately this is the first time I noticed such attitude among python developers.
>
> Importantly the issue is resolved now (did it take a request from IBM's customer to get this implemented ;-) ?) and hopefully a lesson learnt and Christian will be more welcoming and less judgemental of outsiders' contributions.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue38794>
> _______________________________________
History
Date User Action Args
2021-04-03 17:06:49yossariansetrecipients: + yossarian, christian.heimes, Lukas.Vacek
2021-04-03 17:06:49yossarianlinkissue38794 messages
2021-04-03 17:06:48yossariancreate