| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Welcome, @RaisinTen, and thanks for the pull request! If possible, we'll want to avoid floating an additional patch on a dependency like this, especially for unsupported platforms. I think it would be better to first get #33044 land-able, and then perhaps update zlib.h per doc/guides/maintaining-zlib.md. I don't know if that will fix your issue or not, but regardless, I think we want to do that before patching a dependency like this. |
Sorry, something went wrong.
|
Hello @Trott. 🙂 Going through the PR, I understand that we are going to update the zlib-chromium fork regularly. In that case, my change, which is basically a change to the zlib files would end up getting erased on updates. So, I should add my change to deps/zlib/zlib.gyp probably which the PR author was working on. I'd love to help but I'm not sure how I can make changes to his PR to help land it. What should I do? |
Sorry, something went wrong.
|
@nodejs/zlib Thoughts on this? I guess we can land this and then it will be over-written if #33044 ever lands. But there's a danger that will be stalled for a long time. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
I don’t really see how this could hurt, so yeah, if it passes CI I’m good with it :)
Sorry, something went wrong.
|
Hey @Trott, do you know when we can land this PR? It's taking a long time, so I was wondering. |
Sorry, something went wrong.
PR-URL: nodejs#35679 Fixes: nodejs#35629 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com>
| Back | FazBrowse Home | New Git URL |
closes:
Checklist