Starting with version 2.1.0 the Rivet command set moved into the ::rivet namespace.
In order to preserve out of the box compatibility with existing scripts, Rivet exports commands by default and makes them available for import into any namespace (global namespace included). Rivet's build system can be told not to export the command set by passing the switch --disable-rivet-commands-export to 'configure'. In the future we may change this option's default.
Commands must be imported into another namespace with the command:
namespace import -force ::rivet::*
Whenever a new application is being developed and compatibility issues can be confined within specific files, it is recommended that commands be specified with their fully qualified names.