Skip to content

Conversation

@preshanth
Copy link
Collaborator

I have created a package inside the spack directory. If one were to copy parafeed dir into your local spack repo you should be able to install parafeed in your environment by simply saying

spack env create parafeed
spack env activate parafeed
spack add parafeed
spack concretize
spack install 

@sanbee
Copy link
Owner

sanbee commented Jun 10, 2025

Need more precise information for testing.

"If one were to copy parafeed dir into your local spack repo...": Where in the spack repo does this spack directory needs to be copied?

I presume this is way of installing is for testing for now. Ultimately spack install parafeed should be sufficient.

@preshanth
Copy link
Collaborator Author

preshanth commented Jun 10, 2025

spack repo create local_repo local_repo # The second is the namespace
spack add local_repo
cp -r spack/parafeed local_repo/spack-repo/local_repo/packages/
spack install parafeed

That should allow you to test the install. Eventually when its in spack you will install with spack install parafeed it should come from the central repo then.

@preshanth
Copy link
Collaborator Author

If you refer to the Fixing spack install artifacts the last two commits are passing. I have put in a conditional argument that spack building only occurs when spack related files are altered. This is ready to be merged now.

@sanbee sanbee merged commit 18b6355 into sanbee:master Jun 12, 2025
2 checks passed
@sanbee
Copy link
Owner

sanbee commented Jun 12, 2025

I tested it with a bare-bones spack env and the parafeed installation in spack worked. So, merging this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants