Hi Soren,
it is not so clearly documented but: Up to now the only dependencies which influences the product sequence are between setup actions resp. installed status since the product sequence is conceived as product installation sequence, and we would run into contradictions if we tried to follow both kinds of dependency declarations. It is already a typical case which you describe: Some addon B must be installed
after its parent product A. but should possibly be uninstalled
before A. Therefore we get two contradictory sequences for uninstallation and installation but we need a unique sequence.
To solve this problem we have indeed got the idea to produce an uninstall sequence of products and a installation sequence of products (and possibly each product may appear twice).
At the moment, you can handle your task by using opsiservicecalls in your opsiscript to force the other product to be uninstalled (cf.
http://download.uib.de/opsi4.0/doc/html ... erviceCall )
I hope this is helpful
Greetings
Rupert