CMT Problems
Please report here, as precisely as you can, any general or
specific problem you have with the use of CMT. Some of the problems
here will probably be redeclared later as JIRA items.
Container packages
One of the problem encountered in MRvcmt is the following: I'm using the command "cmt show packages" to have the list of the packages contained in the cmtpaths. If some packages belongs to a subdirectory of the cmtpaths and this subdirectory is not a package itself, such contained packages are not shown in the output of this command and so will not shown in the tree of MRvcmt.
This is not a bug of CMT, I think it is a feature; but sometime it could be helpful to just have directories that can contains packages without the need for them to be a true cmt package.
In general this is due (imho) to the fact that in CMT container packages have two roles:
- on one side they are just container; actually, if you use a contained package you will write in your requirements file something like "use Geant4 v2r6* IExternal" and you never specify a version for "IExternal", i.e. you are using it exactly as a directory, not as a package
- on the other side they need to be packages, so they need to have the normal package structure (cmt directory and so on), to be seen from cmt (and so from the current version of MRvcmt).
This double role can create more subtle effects, for example if you have two versions of a container package, as I've tried to describe here http://www.fisica.uniud.it/~glast/MRStudio/history.html (in fact I'm tring something different from MRvcmt in the incoming MRStudio).
Last problem (that is also reported in some JIRA issues cited below), the command of cmt to show packages has some problem that prevent to show all the packages contained in a container package (and again this is reflected in an incomplete tree of MRvcmt .. also for this, MRStudio will not use cmt to build the packages tree, but it will use a paths traversal search with regular expressions).
Tag and Branch Name Confusion
We have run into this problem both for EM and GR when creating branches. For example, if there is a tag called v6r4 on GlastPolicy and then later someone creates a branch on GlastPolicy named, ScienceTools-v6r4 - the next time we go to checkout a package using GlastPolicy v6r4 using CMT, we will receive the ScienceTools-v6r4 tag and not the v6r4 of GlastPolicy. It seems CMT searches for the first instance of the string "v6r4" rather than literally searching for just that particular tag name.
Problem 2...
CMT Items in JIRA