-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
tools: delete macos installer postinstall script #57661
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
Open
sdavids
wants to merge
1
commit into
nodejs:main
Choose a base branch
from
sdavids:users/sdavids/fix/57660
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That doesn't seem correct, we don't want to install those on the release machine
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can either place these files on the release machine before invoking
pkgbuildand then they are inside the package and no postinstall is needed or you need the postinstall script.One could remove them right after the
pkgbuildthough.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am also unsure what you mean by "release machine".
These symlinks are created inside the build folder
outwhich is gitignored.Note: The
lrwx------is due to my machine havingumask 022; on a regular build machine it will belrwxr-xr-x.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving the
unlinkcall to after invocatingpkgbuildsounds like a better solutionUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unlink $(MACOSOUTDIR)/dist/node/usr/local/bin/npxThe
unlinks are for thenpmandnpxsymlinks in thenodeand not thenpmdirectory; these would have been placed in theorg.nodejs.node.pkgpackage—the reason being that they won't end up in the package and will not get extracted to/usr/local/binon the machine the installer is executed on.The symlinks created by this PR will be placed in the
org.nodejs.npm.pkgpackage and thereby the installer will extract them into/user/local/binwith the correct permissions and user/group.One could add 2 additional
unlinkstatements fornpmandnpxafter thepkgbuildthough.But I am not sure if it is worth it: Aren't these links in an ephemeral directory on a build machine?