Hi Jim,

Any update ? Would be great if you could integrate the topic referenced above.

When this is done, add a note on that issue: https://github.com/Slicer/ExtensionsIndex/issues/31

Thanks
Jc

Jc,

I didn't understand the previous status. I didn't realize that you had fixed the issues in your repository already.

Do I understand the process correctly? Instead of sending pull requests to the master repository, we put an issue on the master repository and list the issue in the commit message of the forked repository? This seems to list the commit on the master repository activity page. Is this correct?

Hi Jim,

Indeed, that the idea. The process explaining how to contribute a new extension description [1] is similar to the one associated with extension update/fix contribution.

[1] https://github.com/Slicer/ExtensionsIndex#contributing
[2] TBD

Jc,

What is the recommend mechanism for testing these changes?

Grabbing your changes is not an issue.

But to build with your changes, I either

1) Have to already have the extension built so I can descend directly into the build tree to build against the modifications

2) Locally modify the s4ext file so it points to my local repo and commit

Try on your workstation by submitting an experimental upload.

If possible, try also on the other platform. Ideally, we should have a next and master branch on the extension index ... that's plan for later.

For now, when you think you have something working, update the extension description .. then push a topic on your extension index fork. The commit should reference the issue i entered on the extension index issue tracker.

The problem is that a "make" in ExtensionIndex-build causes the version of the code in the s4ext to be used. Is the only recourse to temporality modify the s4ext file to point to my local repository and the local commit to verify the changes before I push the changes to the master repository?

If you following that approach, simply locally update your local extension description file to point to your fork of carma extension or something along the line. I am not sure to understand what the issue here.

Would be great if you could join the hang out later so that we can clarify the issue.

Fixed - See https://github.com/Slicer/ExtensionsIndex/commit/f7aaf7f9906049326221f41ce0062a5333ad6cb1

Dear issue reporter,

Good news :) Slicer developers SOLVED the problem you reported - YOU now need to VERIFY and CLOSE this issue.

Closing resolved issues that have not been updated in more than 3 months