Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

community/nodejs-current: switch to python3 for building #12138

Closed

Conversation

timbru31
Copy link
Contributor

No description provided.

@probot-autolabeler probot-autolabeler bot added the R-community Community repository label Nov 20, 2019
@timbru31 timbru31 force-pushed the feature/update-nodejs-current branch from 8157eaf to 9648603 Compare November 20, 2019 11:45
Copy link
Contributor

@andypost andypost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It needs more then one patch

zlib-dev libuv-dev openssl-dev c-ares-dev nghttp2-dev"
subpackages="$pkgname-dev $pkgname-doc"
provides="nodejs"
replaces="nodejs nodejs-lts" # nodejs-lts for backward compatibility
source="https://nodejs.org/dist/v$pkgver/node-v$pkgver.tar.gz
dont-run-gyp-files-for-bundled-deps.patch
link-with-libatomic-on-mips32.patch
fix-gyp-python3-incompatibility.patch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's more then it in nodejs/node-gyp#1972

@timbru31
Copy link
Contributor Author

The question we should discuss is if we want to include so many patches and differ from the upstream release or just wait a bit longer until the upstream release is actually python3 compatible.

@andypost
Copy link
Contributor

Better to wait, sametime gyp related update #12144

@timbru31 timbru31 force-pushed the feature/update-nodejs-current branch from 9648603 to f7d16bf Compare November 26, 2019 10:57
@timbru31 timbru31 closed this Nov 26, 2019
@repo-lockdown
Copy link

repo-lockdown bot commented Jan 3, 2020

This repository does not accept Pull Requests (PR) anymore. Development has moved to https://gitlab.alpinelinux.org/alpine/aports Please signup and create a Merge Request (MR) instead. Sorry for the inconvenience caused.

@repo-lockdown repo-lockdown bot locked and limited conversation to collaborators Jan 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
R-community Community repository
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants