[platform-update-dev] Filters for eUpdate

[James D Miles <jdmiles@xxxxxxxxxx>]

It is not clear to me that we have adequate filters for features.
We have
os = {win32, linux, aix, solaris, hpux, qnx, macosx, unknown}
arch = {x86, PA_RISC, ppc, sparc, x86-64, ARCH_X86_64, ia64, ia64-32}
ws = {win32, motif, gtk, photon, carbon, unknown}

What would be the preferred way to prevent eUpdate from attempting to load a feature that expects a full blown platform. Chances are good that the required features or plugins would not be satisfied but that will give an error. Shouldn't we have a filter to handle this?