Move artmod tool to art itself?
artmod tool appears designed to help generate skeleton plugin source code for clients of art. As it therefore generates code that uses art objects, the tool would seem to be better placed in art itself. Art would then install the tool, making it easier for clients to use without having to install another package. Whilst I might be missing a use case for
artmod, I can't think of one where it would be used without art needing to be present to compile the resultant skeletons (i.e. the tool is always associated with an art install/development environment).
#1 Updated by Christopher Green about 5 years ago
- Status changed from New to Accepted
The artmod tool was in art originally, but was moved out because it also supported generation of a plugin skeleton used in the artdaq package. Since support of artdaq has transitioned to a different group, it would make sense to separate out this functionality and put artmod back in to the art package. We need to be careful how to manage this transition however, due to the needs of users of older versions of art.