-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make addpackage check the current dir is inside of CMSSW_BASE #29
Comments
The code is there, albeit commented. The problem is that at FNAL they have the bad habit of creating the workarea in one place and then work in a directory mounted in a different place which makes that code (and the solution you propose) fail. I'll try to think something smarter. |
On 8/2/13 8:40 PM, Giulio Eulisse wrote:
Ciao Giuliio, If we don't want to do it by default, Thanks
Vyacheslav (Slava) Krutelyov |
ping I find that it can be very creative: I deleted the test release area, started a new one and forgot to do cmsenv. What do you know, there was no failure doing git cms-init etc and it recreated back my old release area tree (well, only the src part of it). |
I sometimes forget to cmsenv before running git, after switching from another release area.
Current behavior of cms git tools (cms-addpkg) will make changes
to the old release area, making silently quite a mess.
Please add a check that the current dir is inside of CMSSW_BASE
The text was updated successfully, but these errors were encountered: