[p4] Trigger to restrict users to delete any file

[Lee Marzke]

It's very uncommon to need to obliterate large number of files - the only
obliterates should be for rare accidents.

If your developers are checking in files to the wrong branch or locations,
I would investigate fixing that problem. Restrict check-in to valid 
locations.

If you are refactoring ( moving files and/or directories around ) you
should be doing this in a separate branch, and following the advice
in "Practical Perforce", on handling structural changes.

In short - your proposed solution of restricting delete - would only make
things worse for the developers. In reality, the real solution may involve
better training for your developers, or changing code line policies.

Why not explain your problem much more fully here, and let someone
help you out with a better solution.


Regards,

Lee Marzke

- C Saha - wrote:
> Hi All 
>    
>   I want to keep a close watch to the perforce developers / users regarding file deletions. Users are deleting files using “Open for Delete”  - > “Submit” and then they are not running “pr obliterate” to remove the file permanently. This is causing a big problem and we the depot now containing lost of unused files (and they will not use those files in future also). 
>    
>   So I am planning to implement a trigger which will restrict the all the users to delete (p4 delete) any file. Only super users should be able to do that. 
>    
>   Can anyone help me in doing this? 
>
>
> Thanks a lot to all in advance 
>
> ====================
> Thanks & Regards 
> CSaha
> 		
> ---------------------------------
> Ring'em or ping'em. Make  PC-to-phone calls as low as 1¢/min with Yahoo! Messenger with Voice.
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>