[news.eclipse.tools.buckminster] Re: Buckminster updating / change-list

[Thomas Hallgren <thomas@xxxxxxx>]

Peter M. Murray wrote:
> Hi Thomas,
>
> I'm struggling with understanding that UPDATE/REPLACE should suppress 
> both workspace and target platform resolution.  I have cqueries that 
> ultimately want to find target platform components for resolution.  The 
> cquery is not materializing those elements (e.g. equinox plugins).  If 
> UPDATE suppresses finding them at all, wouldn't the resolution fail in 
> that case?
Right. Something is wrong with that idea :-). We cannot suppress target platform resolution since we don't know how the 
TP was originally populated. Not in it's present shape.

The correct way to resolve this is probably to change how the p2 materializer configures the target platform definition. 
Currently, we just use a "Directory" container and put everything there. This could be more sophisticated so that we 
generate one or several "Software Site" containers that uses a slicer by default. A "Software Site" knows its origin and 
knows how to perform an update. It would also give the user a better experience when accessing the TP definition in the 
UI. Not sure how to go about listening to the update events though.

Perhaps you should defer the TP update for now?

Regards,
Thomas Hallgren