Hello Björn, On May 12, 2013, at 12:36 PM, Björn Grüning wrote:
Hi Greg,
The current revision setting is treated as a minimum, so any available updates are retrieved automatically at the time of installation.
if I get that right, we should always have the latest revision installed, regardless of the specified requirement revision. Is that correct?
No, this is not correct. By "minimum", we mean that the revision setting is treated as a minimum within the set of changeset revisions up to, but not including, the next installable changeset revision in the change log. For example, assume a change log like this: changset revision Installable revision 0: sjekvub yes 1: jjtofvp 2: htocegy 3: jswofpt yes 4: jaqvkrc In the above example, sjekvub is considered the "minimum revision for revs 0, 1, 2, and jswofpt is considered the minimum revision for revs 3, 4. If a dependency definition defined revision sjekvub, then what will actually be installed is "2: htocegy". This approach guarantees reproducibility. For example, assume revision 0: sjekvub contains version 1 of tool A and revision 3: jswofpt contains version 2 of tool A. If you install 0: sjekvub, then you cannot upgrade beyond 2: htocegy for that specific repository installation. To get version 2 of tool A you have to install revision 3: jswofpt of the repository as a separate installation. This ensures that both versions of the same tool are always available to you for reproducibility. This information is document in the following section of the tool shed wiki: http://wiki.galaxyproject.org/RepositoryRevisions
I do not think that is working atm. It seems its using an exact match.
If you are seeing behavior that contradicts the above information or the information in the tool shed wiki, please let me know some specifics. Thanks!
Ciao, Björn
Even so, it may still make sense to allow for a default of the latest installable revision if the definition lacks a revision value.