Rez Hooks,about academysoftwarefoundation/rez

Comments (1)

nerdvegas commented on August 20, 2024

Mark,

Making Rez more plugin-able is absolutely the way it should go imo. I have
identified a lot of cases recently that point at the need for Rez plugins.
The list I currently have is:

versioning. You should be able to register custom version schemes for
particular packages, via a plugin.
the build system. Rez should not be tied solely to cmake
release hooks as you have mentioned.
repo support. Yes we currently have Svn, git and mercurial support, but
this should be implemented as a plugin.

Aso re configuration, its long past time that Rez not rely on a lengthening
number of env vars for configuration. We need to move to config file
support!

On Sunday, December 8, 2013, Mark Streatfield wrote:

Currently I am maintaining a private branch of Rez with some studio
specific changes.

An example of these changes are a different tag name (we use name-version
instead of just version) and popping an event onto ActiveMQ in rez release
.

Currently this works ok, but I can envisage problems when it comes to
merging Chad's pure python changes. And on an ongoing basis we'll have to
do some merging/patching as Rez continues to evolve.

Would there be a benefit to considering plugins for the Rez architecture?
The repository strategy is already a plugin of sorts with Git/Svn/Mercurial
being chosen at runtime, but perhaps this idea could be extended? Some of
the issues (such as tag naming) would be resolved with improved
configuration, however sending events is very studio specific and most
likely only configurable in real python.

This would be easier to implement with Chad's pure python changes too.
What do you think?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/45
.