IPM update procedure is not described

[janihur]

I'm going to update from 0.7 to 0.9 and I don't see the update procedure described anywhere.

All I can find from the fine manual is:

Import it into IRIS and compile via any desired way

What happens if I do:

NAMESPACE>set sc = $system.OBJ.Load("/<PATH>/zpm-0.9.1.xml","ck")

on top of 0.7.x installation?

This is not (yet) a show-stopper as my "update" is really a new install.

[janihur]

Related question: is importing the same version of IPM idempotent? I.e. is it always safe to run

NAMESPACE>set status = $system.OBJ.Load("/<PATH>/zpm-0.9.1.xml","ck")
NAMESPACE>zpm "enable -map -globally"

any number of times.

I'm incorporating IPM installation into our tooling and I'd like to hide all these details from the users so they can always just type:

$ iris-tool install ipm

in operating system command line and get the right IPM version defined by our tooling without nasty side-effects.

[janihur]

Not exactly upgrade related but an installation pattern documentation issue anyway. Am I right that:

IPM supports two different installation patterns:

• Install a version in one namespace (preferably %SYS) and then map the version in to any other namespace. This way all the namespaces in an IRIS instance share the same IPM version.
• Install a version in the every namespace. This way the different namespaces can have different versions.

These patterns can be mixed in the same IRIS instance, but it's probably not a good idea to mix them, YMMV.

I would like to see text like this explaining the big picture with the supporting IPM commands in the docs.