UpdateBot: Nightly -> 4.4

2014-12-25T06:52:34Z

Nightly -> 4.4

New page

<noinclude>{{documentation/versioncheck}}</noinclude>
= Overview =

Extensions can be fully described with an [[Documentation/{{documentation/version}}/Developers/Extensions/DescriptionFile|extension description file]] (*.s4ext). This file is automatically generated in the build tree of your extension.

<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li>For extension source code associated with git repository, for Slicer revision < [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22231 r22231], the automatic generation will extract the read/write url.(i.e <code>git@github.com:jcfr/MyExtension.git</code>) whereas the read-only one is expected (i.e <code>git://github.com/jcfr/MyExtension.git</code>). For details see issue [http://www.na-mic.org/Bug/view.php?id=2032 2032] and [http://www.na-mic.org/Bug/view.php?id=2395 2395]</li>
</ol>

To make your extension available for download to Slicer user, this file need to be added to the ExtensionsIndex repository.

You can think of the ExtensionsIndex as a repository containing a list of extension description files (*.s4ext) used by the Slicer extensions build system to build, test, package and upload extensions on an extensions server.

= Prerequisites =
* Extension belongs to Category 1 or Category 2 as described in [[Documentation/{{documentation/version}}/Extensions/CatalogPolicies|Slicer requirements]]
* Extension has been built, tested and installed on at least one platform (Linux, MacOSX or Windows)

= Contributing a new extension =

== Extensions build against Slicer trunk ==

The following instruction describes how to contribute extension description file for an extension being built against slicer trunk.

<ol start="1" style="list-style-type: decimal;">

<li>Fork the <code>ExtensionsIndex</code>: http://github.com/Slicer/ExtensionsIndex. Click [http://help.github.com/forking/ here] for forking instructions.</li>

<li>Clone your fork, then create a topic named <code>add-<ExtensionName></code></li>
<pre>
git clone git@github.com:USER/ExtensionsIndex SlicerExtensionsIndex
cd SlicerExtensionsIndex
git checkout -b add-YourExtensionName
</pre>

<li>Commit your description file. Commit title should be <code>Add YourExtensionName extension</code> and the content should provide details about the extension.</li>
<li>Push the topic to your fork</li>
<pre>
git push origin add-YourExtensionName
</pre>
<li>
On your github fork, click on "Pull Request". [https://help.github.com/articles/creating-a-pull-request Need help ?]
<ol style="list-style-type:none; border-left:thick solid darkgreen; padding-left:1em;">
<li>Slicer folks will be automatically notified.</li>
</ol>
</li>
<li>That's it !</li>

</ol>

* Consider also reading [[Documentation/{{documentation/version}}/Developers/Extensions/DescriptionFile|Extension description file format]]

== Extensions build against Slicer {{Documentation/currentversion}} ==

* Follow instruction reported in section [[#Extensions_build_against_Slicer_trunk|above]] and select <code>{{documentation/currentversion}}</code> branch when creating the pull request.

= Requesting an extension update =



== Extensions build against Slicer trunk ==

The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.

<ol start="1" style="list-style-type: decimal;">

<li>Update the <code>master</code> branch of both your local clone and your online <code>ExtensionsIndex</code> fork</li>
<pre>
git remote add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex
git fetch upstream # Fetch change of the authoritative ExtensionsIndex
git checkout master # Checkout master
git reset --hard upstream/master # Reset your local master branch using the authoritative master
git push origin master # Update the master branch of your online fork
</pre>

<li>If needed, create branch named <code>update-YourExtensionName</code></li>
<pre>
git checkout -B update-YourExtensionName master # Create branch update-YourExtensionName or ensure the existing one starts of updated master
</pre>

<li>
Regenerate the <code>YourExtensionName.s4ext</code> file by configuring your extension with CMake
<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li> If the svn server needs a username and a password, edit the newly generated <code>YourExtensionName.s4ext</code> file specifying <code>svnusername</code> and <code>svnpassword</code></li>
</ol>
</li>
<li>Commit the <code>YourExtensionName.s4ext</code> file to your cloned ExtensionIndex repository (provide a meaningful commit comment)</li>
<li>Push modifications to your <code>ExtensionIndex</code> fork on github</li>
<pre>
git push origin update-YourExtensionName --force # Publish the updated branch on your fork
</pre>

<li>
Create a "Pull Request" using a link similar to the following: <code>https://github.com/USER/ExtensionsIndex/pull/new/update-YourExtensionName</code>

<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li>
Note: If you are using github for hosting your extension source code, make sure to associated a '''Compare View link''' showing the differences in the source code of your extension (NOT ExtensionIndex!!!) between the previous and current revisions. Compare link is very helpful to summarize the changes.
<pre>
You can build the compare view URL manually with the following format:

https://github.com/USER/REPO/compare/[USER:]GIT-REF…[USER:]GIT-REF

USER is your GitHub username, REPO is your GitHub repository, and GIT-REF can be a tag, branch, or commit SHA1.
</pre>
Source: http://jbuckley.ca/2011/09/githubs-compare-view/

As a concrete example, in [https://github.com/Slicer/ExtensionsIndex/commit/d8c064ea6f5b182fcf0b1b5c86c03afbd5853de5#diff-d5a6aa1d87d84077acf9eaf33bfcde05 this commit] the version of the LongitudinalPETCT extension was changed from 9b6d4b8 to d033772. The extension repository is located here: https://github.com/paulcm/LongitudinalPETCT/, and therefore the compare link is https://github.com/paulcm/LongitudinalPETCT/compare/9b6d4b8...d033772.

</li></ol>

</li>

</ol>

== Extensions build against Slicer {{Documentation/currentversion}} ==

The following instruction describes how to contribute extension description file updates for an extension being built against slicer {{documentation/currentversion}}.

<ol start="1" style="list-style-type: decimal;">

<li>Update the {{Documentation/currentversion}} branch of both your local clone and your online ExtensionsIndex fork</li>
<pre>
git remote add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex
git fetch upstream # Fetch change of the authoritative ExtensionsIndex
git checkout 4.3 # Checkout 4.3
git reset --hard upstream/4.3 # Reset your local 4.3 branch using the authoritative 4.3
git push origin 4.3 # Update the 4.3 branch of your online fork
</pre>

<li>If needed, create branch named <code>update-YourExtensionName-{{Documentation/currentversion}}</code></li>
<pre>
git checkout -B update-YourExtensionName-4.3 4.3 # Create branch update-YourExtensionName-4.3 or ensure the existing one starts of updated 4.3 branch.
</pre>

<li>Regenerate the <code>YourExtensionName.s4ext</code> file by configuring your extension with CMake</li>
* See https://github.com/Slicer/ExtensionsIndex#build-your-own-set-of-extensions-against-slicer-trunk-build-tree.
* If the svn server needs a username and a password, edit the newly generated <code>YourExtensionName.s4ext</code> file to add this information.
<li>Commit the <code>YourExtensionName.s4ext</code> file to your cloned ExtensionIndex repository providing a meaningful commit comment.</li>
<li>Push modifications to your <code>ExtensionIndex</code> fork on github</li>
<pre>
git push origin update-YourExtensionName-4.3 --force # Publish the updated branch on your fork
</pre>

<li>
Create a "Pull Request" using a link similar to the following: <code>https://github.com/USER/ExtensionsIndex/pull/new/update-YourExtensionName-{{Documentation/currentversion}}</code>

<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li>
Note: If you are using github for hosting your extension source code, make sure to associated a '''Compare View link''' showing the differences in the source code of your extension (NOT ExtensionIndex!!!) between the previous and current revisions. Compare link is very helpful to summarize the changes.
<pre>
You can build the compare view URL manually with the following format:

https://github.com/USER/REPO/compare/[USER:]GIT-REF…[USER:]GIT-REF

USER is your GitHub username, REPO is your GitHub repository, and GIT-REF can be a tag, branch, or commit SHA1.
</pre>
Source: http://jbuckley.ca/2011/09/githubs-compare-view/

As a concrete example, in [https://github.com/Slicer/ExtensionsIndex/commit/d8c064ea6f5b182fcf0b1b5c86c03afbd5853de5#diff-d5a6aa1d87d84077acf9eaf33bfcde05 this commit] the version of the LongitudinalPETCT extension was changed from 9b6d4b8 to d033772. The extension repository is located here: https://github.com/paulcm/LongitudinalPETCT/, and therefore the compare link is https://github.com/paulcm/LongitudinalPETCT/compare/9b6d4b8...d033772.

</li></ol>

</li>

Documentation/4.4/Developers/Tutorials/Contribute Extension Description File - Revision history

UpdateBot: Nightly -> 4.4