Skip Menu |

This queue is for tickets about the ClearCase-Wrapper CPAN distribution.

Report information
The Basics
Id: 15136
Status: resolved
Priority: 0/
Queue: ClearCase-Wrapper

People
Owner: Nobody in particular
Requestors: takeo.komiyama [...] freescale.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.11
Fixed in: (no value)



Subject: mkelem -rec
like below directory dir_base/ <--- Clearcase dir dir1/ <--- view private file dir2/ <--- view private file When I invoke like clearcase.plx mkelem -rec dir1 on dir_base/ , script also involve dir2 ( and it seems everything under dir_base is involved ) Is this a spec? or bug?
Date: Wed, 19 Oct 2005 10:17:14 -0400
To: bug-ClearCase-Wrapper [...] rt.cpan.org,undisclosed-recipients:;
From: David Boyce <dsb [...] boyski.com>
Subject: Re: [cpan #15136] mkelem -rec
RT-Send-Cc:
At 07:01 AM 10/19/2005, Guest via RT wrote: Show quoted text
>This message about ClearCase-Wrapper was sent to you by guest <> via >rt.cpan.org > >Full context and any attached attachments can be found at: ><URL: https://rt.cpan.org/Ticket/Display.html?id=15136 > > >like below directory > dir_base/ <--- Clearcase dir > dir1/ <--- view private file > dir2/ <--- view private file > >When I invoke like > >clearcase.plx mkelem -rec dir1 >on dir_base/ , script also involve dir2 ( and it seems everything >under dir_base is involved ) > >Is this a spec? or bug?
This is as designed. The -dir/-rec/-all flags do not take arguments; once you say -rec it will operate on everything under the cwd. It may be a bug that it doesn't warn you the 'dir1' argument is superfluous. Note that ClearCase-Wrapper is smart enough to include the current directory (and any view-private parent directories) in its search. Therefore the right way to mkelem dir1 but not dir2 in your situation is to cd into dir1 and then do a "ct mkelem -rec" from there. It will detect that "." is view private and make it an element. One caveat about this feature - the shell will be confused about its cwd when ct returns because "." now has a different inode. At least in the ksh you can deal with that by issuing a "cd $PWD" afterwards. Depending on view parameters you may need to also flush the view cache. So this is the sequence I typically go through in this case: % ct mkelem -rec -ptime -ok % ct setcs -curr % cd $PWD -David Boyce
This was really resolved long ago, just cleaning up the state. Works as designed.