-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hooks for package caching? #1811
Comments
What OS are you on? Rez uses |
Oh, good point - I forgot to mention this is on Windows, using ACL, so things aren't so simple Specifically the release hook runs something like |
Since packages are copied as the user currently running the rez command you can end up with interesting permissions problems on a shared machine (multiple shifts, renderfarm, ...) If some sort of hooks are added to package copying we would also most likely need hooks for when a package is cleaned from the local cache. |
Just to put this out there without having really thought it through. I was wondering in the past if the actual copying should be pluggable like VCSs. That would also open up rather easy ways to implement things like zipped payloads nor non-filesystem sources maybe |
I would like to, somehow, make the pkg-cache directory read-only - so packages can be added and removed, but their contents not altered by the user
Motivation
For example a Rez package might contain a template file someone might open for reference, but they should not be able to accidentally save over it.
We have a post-release hook which removes write-permissions from released packages. This helps prevent accidental modifications to installed packages.
However if the package package is cached, this gets copied to a writable location, so it's possible to accidentally change something, which can be equally confusing
The text was updated successfully, but these errors were encountered: