In fact, the CDash informs the correct extension git hash (link http://slicer.cdash.org/index.php?project=Slicer4&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=Anom)
and I’ve already tested the package generated there on Slicer (loading this
compressed file in the Extension Manager “install from file” option). In
this way, the extension works fine. However, when I look at the Extension
Manager list, it continues showing a previous version of my extension (git
hash b13577f).
What am I doing wrong here? How can I update my extension correctly to the
Extension Index?
In my machine, I have two version of Slicer. One to developing and another as a user (in order to have access to the extension manager).
I only added a manual path to my extension to the developer version. I use the user-like Slicer just to check if the extension is normally available in the server.
Do you think that it may cause a conflict?
Since the API and ABI of the nightly version of Slicer can change from one day to an other, we rebuild all extensions everyday. This effectively means that user using nightly build will have to download a recent nightly to get the latest version of the extension.
On the other hand, if the extension description file associated with release 4.6.2 is updated, user already having installed the stable version of slicer will be able to simply update the extension. This will work if the extension maintainer update the description file associated with that version.
For any given extension, being able to use the same code in both the last release and the nightly means that you consider API changes in the code … or maintain two version of the code.