On 2026/07/26 15:06, Anoduck, The Anonymous Duck wrote: > Announcing Curl-Impersonate to OpenBSD Ports Tree. > > This is my first contribution to ports, and something I have wanted to contribute to for a long time. So, be gentle guys. > > Currently hosted at: https://codeberg.org/anoduck/curl-impersonate-port > > Will try to submit pull request to Jasper's OpenBSD-WIP repo in the next week or two to begin staging for inclusion. That port is doing a lot of things which are at odds with how ports should work. Due to how this is built upstream (i.e. files from various upstreams which need patching), it's necessarily going to be a bit of a mess, but we can get closer at least, see attached tar. This project builds a patched curl with static-linked boringssl (with C++ code); curl-impersonate upstream have been stumbling around trying to figure out how to add the C++ standard library via 'cc -l<name>' with all sorts of mess to try and figure out which library to use - instead they should just use c++ to link. I haven't figured out how to get that done directly in the standard build but did come up with a pretty horrible workaround. If any cmake wizards want a challenge, try to get it to link the executable directly with c++ as part of the main build rather than the post-build monstrosity...you may end up having to patch a patch. > POI: Tried to generate the PKLST last night, but go-tools was unavailable. So, will add when the package comes available again. Not sure why you need go-tools to generate a plist? (Most of the BUILD_DEPENDS listed were bogus too, though I see they do come from upstream). > Would be super cool if I could port over the python library as well. That is likely to be a problem. boringssl is statically linked into libcurl-impersonate.so and trying to load this into the same address space as python will likely result in a conflict with the libressl ones used by python. > Cheers, > Anoduck > > # =========================== > Anoduck, The Anonymous Duck > > https://anoduck.github.io/wiki/ > https://github.com/anoduck > https://anoduck.com > https://codeberg.org/anoduck >
No comments:
Post a Comment