Tim Leavitt

The intended workflow around this needs better documentation.

There's a FileCopy resource processor just for this. Needs to be documented.

Similar to #254 - this is OK if it's a folder/package-level equivalent but not *.LUT, etc.

For backward compatibility I think the right approach would be adding an "interactive" flag for install/load that can be checked in package-specific code (with corresponding documentation). This should be done.

Note, one approach here (which my team has used to a limited extent) would be a %Studio.AbstractDocument wrapping XML import/export of a Security.* object. This is really something that belongs...

We already have a flag to turn transactions off - in zpm install and load you can add: ``` -DNoTransaction=1 ``` You can also set this up as a default...

Good point, I read too quickly. More investigation is needed, just throwing some ideas: The quick operational solution would be to increase locksiz (and perhaps gmheap). Short of that, we...

@canzanos in your example error message what's Module A, what's Module B, and what are you trying to install? This looks like rclib-fhir (already installed) needs a specific version of...

It would be good to improve the error message here to explicitly state that there are conflicting version requirements, rather than indicating that we can't find a version that satisfies...

From a resource naming perspective, there's a lot of meaning (and dependencies in code) where a name starting with "/" indicates something on the filesystem and a name that doesn't...