Geoffrey wrote in:
http://www.novell.com/communities/no...igner-4-part-1

"Filters had to be broken up in a similar fashion, but were handled
differently, via extensions. Filter extensions are a critical point, the
filter is still one gigantic XML blob. However filter extensions allow
packages to contribute filter fragments to an installed driver. When
uninstalling packages, Package Manager checks each filter piece and if
the last contributing extension for any part of the filter has been
removed, that part of the filter will be removed as well."

Does anyone know what rules are used to determine what wins if several
packages each containing a filter extension that refers to the same
filter piece are applied to a package?

For example:

Package 1 contains a filter-ext resource that includes the fragment
(each for a user object):

<filter-attr attr-name="CN" publisher="ignore" subscriber="sync"/>

Package 2 contains a filter-ext resource that includes the fragment

<filter-attr attr-name="CN" publisher="sync" subscriber="sync"/>

Package 3 contains a filter-ext resource that includes the fragment

<filter-attr attr-name="CN" merge-authority="edir" publisher="sync"
subscriber="sync"/>

All three packages are applied to a driver. How should the combined
filter appear? Does the order in which the packages are applied have any
impact?

Is there any way to force the combined filter to be re-built from it's
constituent extension resource objects? For other objects - there is a
"revert customisation" option but this is not available for the driver
filter itself.