On Wed, Jun 6, 2012 at 12:39 PM, Paul Webster
<pwebster@xxxxxxxxxxxxxxxxxxx> wrote:
During the build p2 took your bundles, features, and any p2.inf and generated metdata IUs and artifact IUs into your final p2 repo. Any p2.inf instructions have been turned into attributes and/or elements of the metadata IUs in the p2 repo. At that point, the p2.inf is just a text file, and isn't necessary.
During an install, the metadata IUs are used/execute (the instructions configure your start levels, etc), and also copied into the profile (like the SDKProfile.profile found in the Eclipse SDK). That's so removing the IUs can execute any unconfigure/uninstall instructions, etc.
Ok, I think I'm getting it. I am looking at our build rules and there we use the FeaturesAndBundlesPublisher to create our "build-time" p2 repository. So what it comes down to is that the p2 director, when it does the install, doesn't need the p2.inf to do the install, all of the IUs have the p2 rules already applied in our "build-time" p2 repository.
I must have understood this at some point because I built all of this, but I guess if you're not doing it daily it can get to be a bit much to remember. Now I just need to figure out how to update our base p2 runtime, finding it hard to even know where to start with that :-P
Thanks much Paul and Thomas, it really helps to have talked about this!
Cheers,
Craig
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
