[news.eclipse.tools.buckminster] Re: P2 materializer and profiles

[Carsten Reckord <reckord@xxxxxxxxxxxxxxxxxxx>]

Hi Thomas,

On 27.08.2009 16:08, Thomas Hallgren wrote:
> That would require some kind of interaction with the director. I.e. Buckminster would find the features to install and 
> then tell the director to perform the actual installation. Is that the use-case that you are after?

That's exactly the use-case I'm after I think. Our runtime is basically assembled from 3 parts (a bare-bone rcp, the features of our target 
platform, and our own features). Since we already have queries, rmaps et. al. in place for all of them for building, creating update-sites 
etc., it seemed natural to use those to assemble the runtime, too, instead of setting up separate scripts for the director.

> In general, the director is what you should use if you want to install things into a product. We ship a headless version 
> of it on our download page. Would that be a solution for you?

I haven't done that so far, because I didn't want to introduce another tool that isn't without its pitfalls and duplicate a good portion of 
the information already existing for buckminster for that.

> The one concerning the NPE is covered already but I don't think there's a bugzilla about the local reader recognizing 
> SCM meta-data.

Okay, I'll enter that then.


Regards,
  Carsten