You can edit the policy and delete all DirXML-pkg attributes in iManager. That will allow you to then delete the policy. But I would probably not do that if the policy is actually in the installed package, only if I ended up in a state where the policy isn't in an installed package, but it think it is.

This is not per se a normal process.

You could copy the package, remove the elements you not want in your package, then remove the original package from your driver and your modified package on instead.

Now it is an editable package you can remove and add stuff to.

Hey Ernesto,

as Geoffrey said: copy the package as new one and modify the policies as needed. Note, however, that the policies from closed packages have an implied copyright of the package-owner.

Other option is to create new package and add policy by policy to that package.

Regards

Philipp Deneu said:

policies from closed packages have an implied copyright of the package-owner.

Or even an explicit copyright, if the vendor bothers to add a license to the package or a (c) note e.g. to the vendor information details, like we do it for all our packages. :-)

Thanks to all for your input.
I don think that deleting unused policies will violate licensing terms. I don't see the need for leaving permanently disabled policies laying around.
If I start by copying the required packages I will need to create a new driver linked to the newly copied packages.
I'm looking for a way to take an running driver and detaching it from the packages it's linked to.
That seems to me to be a quicker way to delete unwanted policies and later create new packages as required.
I will experiment with the exported driver XML by removing the contained  package references.

If you import the driver from edir, without having the required packages in your catalog, then all resources are unlinked in your designer project.

Thanks for the hint Philipp. I currently have no access to the IDVault, only the Designer project.

Export driver from Designer into an iManager Config file.  Find the package references with a GUID like value in the XML, change them all to 'something else' then reimport. Same result as Philipp suggested.