safe-rm should have a "strict" setting
Bug #1070252 reported by
quazgar
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Safe-rm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I think that safe-rm should have a "strict" setting: If one target is in the black list, the whole rm procedure should be stopped with an exit status of != 0.
This would for example if ~/* was to be deleted, and ~/Documents is protected, this would protect everything else there as well. Much better than having to add every single file :)
To post a comment you must log in.
Using this patch, safe-rm should do what I proposed. It's not configurable yet, that would have to be implemented by someone who actually knows perl.