RELEASE 2.23.0: Package Usage Tracking, Better Config Overrides

Addresses: #528

Two new features are added in this release:

• Override any config setting with an env-var. For any setting "foo", you can now set the env-var REZ_FOO_JSON to a JSON-encoded string. This works for any config setting. Note that the existing REZ_FOO env-var overrides are still in place also; if both are defined, REZ_FOO takes precedence. This feature means you can now override some of the more complicated settings with env-vars, such as package_filter.

• Track context creation and sourcing via AMQP. Messages are published (on a separate thread) to the nominated broker/exchange/routing_key. You have control over what parts of the context are published. For more details: https://github.com/nerdvegas/rez/blob/master/src/rez/rezconfig.py#L414

Other notes:

• The embedded simplejson lib was removed. The native json lib is used instead, and for cases where loads-without-unicoding-everything is needed, utils/json.py now addresses that instead.

RELEASE 2.22.1: Stdin-related fixes

Addresses issues:

• #512
• #526

RELEASE 2.22.0: Search API

PR: #213

Package/variant/family search API is now available in package_search.py. This gives the same functionality as provided by the rez-search CLI tool.

RELEASE 2.21.0: Added mingw as a rez build_system for cmake

PR: #501

RELEASE 2.20.1: Windows Fixes

PRs:

• #490: Fix alias command in Windows when PATH is modified
• #489: Fix cmd.exe not escaping special characters
• #482: Fix selftest getting stuck on Windows

Addresses Issues:

• #389
• #343
• #432
• #481

RELEASE 2.20.0: Better CLI Arg Parsing

PR: #523
Addresses: #492

The rez-python command now supports all native python args and passes those through to its python subprocess - so you can now shebang with rez-python if that is useful.

More broadly, rez commands now parse CLI args correctly for each case. Many commands previously accepted rez-env-style commands (eg rez-env pkgA -- somecommand -- i am ignored), but simply ignored extraneous args after -- tokens.

RELEASE 2.19.1: Fixed bug with rez-build and package preprocess

Merged PR: #522
Addresses: #514

The problem occurred because the preprocess function was attempting to be serialized when the package definition is cached to memcache. However, this function is stripped in installed packages; furthermore, caching "developer packages" (ie unbuilt packages) was never intentional.

This release disables memcaching of developer packages, thus avoiding the bug and bringing back originally intended behavior.

RELEASE 2.19.0: Misc Bugfixes, Minor Feature Additions

• #519: fix typo in create_build_process
• #518: Added /etc/os-release Linux OS detection
• #493: Clarify what variant number is currently building
• #499: Fix whitespace issue in PS1
• #488: Fix selftest by isolating changes in test environment
• #473: allow to user input and packages in rez-env at the same time
• #521: Shell based completion path selection
• #471: added warm option to rez-memcache
• #472: adding no-cache option to rez-gui
• #454: Add standard_system_paths setting to set default PATH

RELEASE 2.18.0: Config improvements

Addresses: #402
Supersedes: #373

• Multiple config files are now supported, set $REZ_CONFIG_FILE to path-like value;
• List appending/prepending rather than straight override now supported, see https://github.com/nerdvegas/rez/wiki/Configuring-Rez#settings-merge-rules

RELEASE 2.17.1: CMake-3 fix

Addresses: #450

This release should fix cases on some OS's and CMake-3.x versions, where either a build fail occurred, or an installation quietly skipped files.

Please be aware: This fix will cause 'empty' packages (those with no files to install) to fail during the build, with the message:

make: *** No rule to make target 'install'.  Stop.

The fix is to use the new build_command package attribute, to specify that your package doesn't have anything that needs building. Add this to your package.py:

build_command = False