Tim Leavitt

This would be a major backward incompatibility. It would be better to drive users to better habits through tools.

Fair points. Gut feeling: restrictions on what can be published should be under control of the registry itself, not the package manager. The registry could theoretically inject further constraints about...

This has been encountered internally as well. It would be great for IPM to provide a way to do this in a background job to isolate from the current transaction....

Calling this a enhancement - specifically, we need to provide a "right way" to have an `` do something outside of the transaction and only after installation has fully completed.

@isc-shuliu see ZPM.Installer:ZPMInit - we don't want to overwrite any old/existing settings here.

FYI, here's some relevant work for node/npm: https://github.com/intersystems/isc-ipm-js

> Already implemented in form `[registry-name/]package-name` Oh, nice!

#457 handles all but the clean install + upgrade.

#466 incorporates a change to clean install + upgrade (assuming our upcoming v0.7.1 release as a basis)

I think this was the real issue behind #331