E4S-Project / E4S-Project/e4s

Provide ParaView via Spack instead of via upstream, non-Spack release tarball

Open
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
41
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Where/When possible use Spack to provide ParaView and include the examples from an external source instead of relying on the binary release to install ParaView.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by locating the ParaView installation logic and any Spack configuration in the repository, then identify how examples are currently sourced from the release tarball. Done means ParaView is provided through Spack where possible and the examples come from an external source.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.