-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
bugfix: lua-luafilesystem package should use stage.source_path #11648
Merged
tgamblin
merged 1 commit into
develop
from
bugfix/packages-should-not-assume-expanded-tarball-name
Jun 6, 2019
Merged
bugfix: lua-luafilesystem package should use stage.source_path #11648
tgamblin
merged 1 commit into
develop
from
bugfix/packages-should-not-assume-expanded-tarball-name
Jun 6, 2019
Conversation
This file contains 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
@odoublewen: does this work for you? |
Works for me. Tried to do a quick survey of package.py files to see where else this construct might be lurking. Perhaps these lines in def setup_environment(self, spack_env, run_env):
stage_lua_path = join_path(
self.stage.path, 'Lmod-{version}', 'src', '?.lua') |
Well, the |
I think it probably needs an update. Most of these as well:
|
tldahlgren
approved these changes
Jun 6, 2019
tldahlgren
added a commit
to tldahlgren/spack
that referenced
this pull request
Jun 7, 2019
…#11648). Note that installing `catalyst` fails in the same place it does for the commit prior to merging changes for spack#11528.
tldahlgren
added a commit
to tldahlgren/spack
that referenced
this pull request
Jun 7, 2019
Fixes spack#11528 See also spack#11648 Note that installing `catalyst` fails in the same place it does for the commit prior to merging changes for spack#11528.
carsonwoods
pushed a commit
to carsonwoods/spack
that referenced
this pull request
Jun 27, 2019
dev-zero
pushed a commit
to dev-zero/spack
that referenced
this pull request
Aug 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #11645.
@odoublewen
After #11528, we use
$stage_dir/src
as the path for all expanded tarballs, so that the expanded path is known in advance. This helps client code that needs to know the checked out source path before fetching and expanding the source.Some builds seem to assume they know
stage.source_path
and construct it themselves. e.g,lua-luafilesystem
was doing this:It assumes the name of the directory under stage is
'luafilesystem-{version.underscored}'
. Code like this should usestage.source_path
instead of joiningstage.path
with an assumed name.Here is the fix: