Feature #3197

gmake clean and "job" directory

Added by Mark Messier about 8 years ago. Updated almost 8 years ago.

Start date:
Due date:
% Done:


Estimated time:


Currently a "gmake clean" will remove the .so's and .o's a particular package makes and installs in your release but it will not remove any .fcl files the package may have installed. This can be quite confusing. For example, suppose you:

- check out EventDisplay
- edit evd_services.fcl for a particular task
- build
- run for a while, finish your task
- gmake clean; remove the event display package

From now on in that test release you will always pick up your edited version of the evd_services.fcl file. When new parameters are added in the base release, you will be blind to them causing the display to not start. This is just one example. Similar examples where reconstruction is performed are potentially even more confusing.


#1 Updated by Mark Messier about 8 years ago

  • Priority changed from Normal to Low

Hmm - I might have spoken too soon on this one. This might be related to my own bungling of the CVS to SVN switch over from an existing test release. Working from a brand new SVN test release this behavior seems to be correct. gmake clean seems to do the right thing. Maybe I rmpkg'ed without doing a clean?

#2 Updated by Gavin Davies almost 8 years ago

  • Status changed from New to Resolved

This was a skew between cvs/svn usage.
The correct manner in which to remove a package is to do:

% gmake clean; (not absolutely necessary, but for the paranoid)
% rmpkg -f <package>;

I'm marking this as resolved and closing it.

#3 Updated by Gavin Davies almost 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF