Using absolute path for npm post requirement#243
Closed
atroisi93 wants to merge 1 commit intotelefonicaid:masterfrom
Closed
Using absolute path for npm post requirement#243atroisi93 wants to merge 1 commit intotelefonicaid:masterfrom
atroisi93 wants to merge 1 commit intotelefonicaid:masterfrom
Conversation
Member
|
Thank you for the feedback! We are going to consider the usage of absolute paths in the .spec but in a wider scope, I mean, not only for this repository but for all the ones we are involved based on Node.js. |
Member
|
PRs (some in other repos) related (they implement the change to absolute paths mentioned above): |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using npm instead of /usr/bin/npm causes a bad behaviour on rpm installation. This commit fix the requirements in post step