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

fix: [PROTOTYPE] add option to use symlinks with the npm plugin #1004

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

bepri
Copy link
Contributor

@bepri bepri commented Feb 4, 2025

  • Have you signed the CLA?
  • Have you added an entry to the changelog (docs/reference/changelog.rst)?

@bepri bepri self-assigned this Feb 4, 2025
@@ -301,11 +314,12 @@ def get_build_commands(self) -> list[str]:
cmd += [
dedent(
f"""\
tar -xzf "{self._node_binary_path}" -C "${{CRAFT_PART_INSTALL}}/" \
tar -hxzf "{self._node_binary_path}" -C "${{CRAFT_PART_INSTALL}}/" \
Copy link
Contributor Author

Choose a reason for hiding this comment

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

tar -h avoids overwriting symlinks at the location, instead following them when unpacking a tarball

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Much of the diff in this file was a refactor to deduplicate code into a fixture, the tests themselves are unchanged

@bepri bepri force-pushed the work/npm-plugin-symlinks/CRAFT-4071 branch from e33ee74 to f347293 Compare February 5, 2025 21:03
@bepri bepri changed the title fix: add option to use symlinks with the npm plugin fix: [PROTOTYPE] add option to use symlinks with the npm plugin Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant