Introduce Slicer extensions as packages #98
Draft
+426
−163
Conversation
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
asiangoldfish
force-pushed
the
slicer-modules
branch
from
7375ba5 to
bf9c65e
Compare
Contributor
Author
|
Hi, @RafaelPalomar. As mentioned earlier today on October the 22nd, this is the PR I am currently working on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Goal
This pull requests introduces APIs to create Slicer extensions as packages. The goal is to allow users to install a module as if it was just another Guix package.
Example
With this, Plots should be accessible within the Slicer application. Uninstalling Plots should not affect Slicer at all besides removing the extension from the application.
Checklist