Closed GoogleCodeExporter closed 9 years ago
This is a known problem, partly documented in the wiki:
http://code.google.com/p/clearcase-cpan/wiki/CavComments
There may be bits of solution for special cases, especially on linux/unix,
but so far, I don't have any satisfactory general answer.
Original comment by marc.girod
on 3 Jun 2009 at 12:32
Original comment by marc.girod
on 3 Jun 2009 at 12:35
One way to cope with this until a fix is found, is to use .clearcase_profile or
.clearcase_profile.pl
The former is used by cleartool, and one may prefer to use different defaults
for the wrapper.
The other could drive to either use silently -nc (and -f... or the like),
or to stop unless either -c or -nc would be given,
or to use -nc but warn...
This requires however some support. I don't prioritize it right now.
Original comment by marc.girod
on 5 Jun 2009 at 4:44
I have prolems with the obvious...
Of course, I don't know how to fix this in ClearCase::Argv,
but fixing it in a Wrapper should be trivial.
In fact, the best is probably in ClearCase::Wrapper...
Original comment by marc.girod
on 6 Jun 2009 at 12:17
there is not a problem for now, I mean I'm using -c and -nc
Original comment by fede.naum@gmail.com
on 10 Jun 2009 at 4:22
Implemented for mklbtype in r357.
Need to take into use in the other functions.
Also, this doesn't support the interactive queries with one char reply (e.g.
-rm/-keep)
Treating -cqe forces to run commands in a loop, which fights again the previous
use
of exec.
I tried to support the CLEARCASE_PROFILE environment variable, but there may be
some
strange effects due to prior treatment in both ClearCase::Argv and
ClearCase::Wrapper
(e.g.: order of evaluation).
I didn't (yet?) try to support CLEARCASE_CMNT_PN, or otherwise to offer default
comments for edit.
Original comment by marc.girod
on 19 Jul 2009 at 2:01
Original issue reported on code.google.com by
fede.naum@gmail.com
on 3 Jun 2009 at 4:13