Re: [platform-update-dev] Filters for eUpdate

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

Note that the <feature> filters
for os, ws and arch are not recommended.  The problem is that they
do not list triplets but just lists.  For example linux, win32, carbon
is not a valid configuration but could be construed as one from the current
syntax.  In most cases people have features that supply some function
generically and then as an implementation detail have some platform-specific
plugins.  In that case you are better off using the <plugin>
markup for os, ws and arch (see the RCP feature for an exampel).

Jeff

James D Miles <jdmiles@xxxxxxxxxx>
Sent by: platform-update-dev-bounces@xxxxxxxxxxx

11/08/2005 06:25 PM

Please respond to
"Eclipse Platform Update component developers list."

To	platform-update-dev@xxxxxxxxxxx
cc
Subject	[platform-update-dev] Filters for eUpdate

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?_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-update-dev