Tim Leavitt

Clarifying: this is a *local* history on the instance where the packages are installed.

Would be great to expose this via zpm "history" or something like that, and also to provide a public API for programmatic access.

@isc-kiyer @isc-rkuszews @isc-eneil - could you chime in if you think anything is missing from the spec? This is very important for v1 / inclusion in IRIS.

@SCanzano I view this as an upstream issue in that `##class(%SYSTEM.OBJ).IsUpToDate("Ens.Utils.Tasks.Purge")` definitely should report 1 (and IPM can't do anything about that). This could be worth pursuing via InterSystems Support....

Disclaimer: I haven't used the Flags attribute for ~7 years, but I think it should work!

> @isc-tleavitt I dont disagree with you and this may not have solved my issue but the real question is when running install _moduleName_ should it force the recompile of...

> @isc-tleavitt > > > @SCanzano I view this as an upstream issue in that `##class(%SYSTEM.OBJ).IsUpToDate("Ens.Utils.Tasks.Purge")` definitely should report 1 (and IPM can't do anything about that). This could be...

We have https://github.com/intersystems/isc-codetidy which runs server-side. I've used more client-centric dev patterns for IPM though and I think that's likely to be the more common pattern for contributors.

IMO using different versions with + to distinguish releases with a meaningful order of precedence is bad and goes against the semver spec, and the solution is to actually follow...

I believe the needs here have been addressed between #557 and other recent discussions. (Plus some upcoming discussions about internal processes.)