You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is required to support package archival. What would happen is something like this:
for some pkg repo path (eg /pkgs), you have some archive pkg repo, let's say /archive
to archive a pkg, you 'move' it from /pkgs to /archive
in reality this is a copy + an ignore in the src repo
we don't want to actually delete the src pkg, there is a chance it may still be in use
The actual process would be:
the pkg in /archive is ignored (even though it doesn't exist yet!)
the src pkg is copied to /archive
now, in quick succession, the src pkg is ignored, and the dest pkg is unignored
This causes the pkg to be moved in as atomic a way as possible.
Archival is just a specific case of moving a package. The idea here is that archived pkgs are still kept in archive repos. If an old runtime needs to be recreated, REZ_PACKAGES_PATH can just be updated to include the archive repos. Note that you would want to keep the original pkg timestamps in this scenario (otherwise archived pkgs would think they did not exist previous to time of archival).
The text was updated successfully, but these errors were encountered:
Add rez-pkg-mv op.
This is required to support package archival. What would happen is something like this:
The actual process would be:
This causes the pkg to be moved in as atomic a way as possible.
Archival is just a specific case of moving a package. The idea here is that archived pkgs are still kept in archive repos. If an old runtime needs to be recreated, REZ_PACKAGES_PATH can just be updated to include the archive repos. Note that you would want to keep the original pkg timestamps in this scenario (otherwise archived pkgs would think they did not exist previous to time of archival).
The text was updated successfully, but these errors were encountered: