Difference between revisions of "Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions"
From Slicer Wiki
m (Reverted edits by JChris.FillionR (Talk) to last revision by Fbudin) |
|||
| Line 12: | Line 12: | ||
* Consider also reading [https://github.com/Slicer/ExtensionsIndex/wiki/Extension-description-file Extension description file format] | * Consider also reading [https://github.com/Slicer/ExtensionsIndex/wiki/Extension-description-file Extension description file format] | ||
| − | = Requesting an extension version update = | + | = Requesting an extension version update {{updated}} = |
On your local fork, the idea is to create the following topic branches: | On your local fork, the idea is to create the following topic branches: | ||
* <code>update-<YourExtensionName></code> based of [https://github.com/Slicer/ExtensionsIndex/tree/master <code>master</code>] integration branch. | * <code>update-<YourExtensionName></code> based of [https://github.com/Slicer/ExtensionsIndex/tree/master <code>master</code>] integration branch. | ||
| − | * <code>update-<YourExtensionName>-4.2</code> based of [https://github.com/Slicer/ExtensionsIndex/tree/4.2 <code>4.2</code>] integration branch. | + | * <code>update-<YourExtensionName>-4.2.0</code> based of [https://github.com/Slicer/ExtensionsIndex/tree/4.2.0 <code>4.2.0</code>] integration branch. |
| − | |||
== Extensions build against Slicer trunk == | == Extensions build against Slicer trunk == | ||
| Line 26: | Line 25: | ||
<pre> | <pre> | ||
git remote add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex | git remote add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex | ||
| − | git fetch upstream | + | git fetch upstream # Fetch change of the authoritative ExtensionsIndex |
| − | git checkout master | + | git checkout master # Checkout master |
| − | git reset --hard upstream/master | + | git reset --hard upstream/master # Reset your local master branch using the authoritative master |
| − | git push origin master | + | git push origin master # Update the master branch of your online fork |
</pre> | </pre> | ||
* Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex | * Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex | ||
| Line 41: | Line 40: | ||
* Push modifications to your ExtensionIndex fork on github | * Push modifications to your ExtensionIndex fork on github | ||
* Submit a pull request to https://github.com/Slicer/ExtensionsIndex (provide a meaningful commit comment) | * Submit a pull request to https://github.com/Slicer/ExtensionsIndex (provide a meaningful commit comment) | ||
| − | |||
== Extensions build against Slicer {{Documentation/currentversion}} == | == Extensions build against Slicer {{Documentation/currentversion}} == | ||
| Line 47: | Line 45: | ||
The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk. | The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk. | ||
| − | * Update the 4.2 branch of both your local clone and your online ExtensionsIndex fork | + | * Update the 4.2.0 branch of both your local clone and your online ExtensionsIndex fork |
<pre> | <pre> | ||
git remote add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex | git remote add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex | ||
| − | git fetch upstream | + | git fetch upstream # Fetch change of the authoritative ExtensionsIndex |
| − | git checkout 4.2 | + | git checkout 4.2.0 # Checkout 4.2.0 |
| − | git reset --hard upstream/4.2 | + | git reset --hard upstream/4.2.0 # Reset your local 4.2.0 branch using the authoritative 4.2.0 |
| − | git push origin 4.2 | + | git push origin 4.2.0 # Update the 4.2.0 branch of your online fork |
</pre> | </pre> | ||
| − | * Create a branch named update-<YourExtensionName>-4.2 in the clone of your forked ExtensionsIndex | + | * Create a branch named update-<YourExtensionName>-4.2.0 in the clone of your forked ExtensionsIndex |
<pre> | <pre> | ||
| − | git checkout -b update-<YourExtensionName>-4.2 | + | git checkout -b update-<YourExtensionName>-4.2.0 |
</pre> | </pre> | ||
* Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake | * Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake | ||
Revision as of 20:47, 4 February 2013
Home < Documentation < Nightly < Developers < Tutorials < BuildTestPackageDistributeExtensionsContents
Create a new extension and adding it to the extension index
Obtain an API key to submit on the extension server
Upload an extension in the experimental folder
Contribute an extension description file
- See instructions on github
- Consider also reading Extension description file format
Requesting an extension version update UPDATED
On your local fork, the idea is to create the following topic branches:
update-<YourExtensionName>based ofmasterintegration branch.update-<YourExtensionName>-4.2.0based of4.2.0integration branch.
Extensions build against Slicer trunk
The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.
- Update the master branch of both your local clone and your online ExtensionsIndex fork
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
- Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex
git checkout -b update-<YourExtensionName>
- Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
- 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 <YourExtensionName>.s4ext file to add this information
- Commit the <YourExtensionName>.s4ext file to your cloned ExtensionIndex repository (provide a meaningful commit comment)
- Push modifications to your ExtensionIndex fork on github
- Submit a pull request to https://github.com/Slicer/ExtensionsIndex (provide a meaningful commit comment)
Extensions build against Slicer 4.10
The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.
- Update the 4.2.0 branch of both your local clone and your online ExtensionsIndex fork
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.2.0 # Checkout 4.2.0 git reset --hard upstream/4.2.0 # Reset your local 4.2.0 branch using the authoritative 4.2.0 git push origin 4.2.0 # Update the 4.2.0 branch of your online fork
- Create a branch named update-<YourExtensionName>-4.2.0 in the clone of your forked ExtensionsIndex
git checkout -b update-<YourExtensionName>-4.2.0
- Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
- 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 <YourExtensionName>.s4ext file to add this information
- Commit the <YourExtensionName>.s4ext file to your cloned ExtensionIndex repository (provide a meaningful commit comment)
- Push modifications to your ExtensionIndex fork on github
- Submit a pull request to https://github.com/Slicer/ExtensionsIndex (provide a meaningful commit comment)
1. Create Pull Request
2. Select base
3. Send Pull Request
4. Verify
