| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 7372 | Sven Erik Knop |
Rollback Rename/move file(s). To folder "perforce" is needed. |
||
| #1 | 7370 | Sven Erik Knop | Rename/move file(s) again - this time to the right location inside a perforce directory. | ||
| //guest/sven_erik_knop/P4Pythonlib/triggers/RevisionPurger.py | |||||
| #1 | 7367 | Sven Erik Knop | New locations for the Python triggers. | ||
| //guest/sven_erik_knop/triggers/RevisionPurger.py | |||||
| #5 | 7251 | Sven Erik Knop | Updated the comments | ||
| #4 | 7249 | Sven Erik Knop |
A few name changes. Removed all references to PakRemover and changed the DEBUG message. |
||
| #3 | 7222 | Sven Erik Knop | Added some documentation to RevisionPurger.py | ||
| #2 | 7221 | Sven Erik Knop |
Minor improvements - Renamed the main class to RevisionPurger - Added the ability to keep more than one revisions |
||
| #1 | 7220 | Sven Erik Knop |
Added RevisionPurger.py, a tool to be used as a change-commit trigger that will remove files from the Perforce librarian. It is similar in use like the +S type, but handles branches gracefully. The trigger takes the changelist as an argument , scans through the changelist and finds files that are eligible for delete: - Must have a predecessor revision - Must be of the right type, that is binary full or compressed file - Must have no lazy copies, unless every lazy copy has a successor - Must not be a lazy copy itself, but will follow lazy copies to the parent and apply above algorithm on that revision If all conditions are met, the depot file is removed from the archive, replaced with an empty file and the digest for verify is adjusted. |
||