rez rm

[mottosso]

Goal

Facilitate small companies and beginners of Rez during the initial learning stage and small-scale package management.

Motivation

As you learn about Rez, you'll want to create a lot of packages, a lot of which were for practice. Removing packages currently involves manually deleting a directory on disk, and doesn't account for deleting packages other than from file-system repositories. It also prevents tracking of deleted packages (for e.g. archival), if deleting happens outside of Rez.

Implementation

Like rez cp, add a rez rm command that does as advertised.

$ cd mypackage
$ rez build --install
$ rez rm mypackage

Conditions

• If a package exists in more than one location, delete only the first found; the same you get from rez env, and provide a message informing the user of such.
• For non-local packages, defer to permissions to determine whether or not a user is allowed to delete; in a large scale environment the command is only relevant to local development packages, but in small studios where write-access is everywhere and flexibility outweighs stability it would apply there as well.

[mottosso]

This should also help tackle the issue of memcache holding onto packages post-deletion, as would typically be the case by manually deleting from outside of Rez. As memcached would have no reason to think a package has been deleted, without actually going out and querying the disk; defeating the purpose of caching in the first place.

[mottosso]

It should also manage cleanup after removing a variant.

E.g.

~\packages\PySide\1.2.4\platform-windows\os-windows-10\python-2.7

• Removing this variant should also delete 1.2.4 if this was the only variant.
• It should delete PySide if it was the only version.

Otherwise, we'd end up with gaps all over the place.