Hey Pascal, you're previous message was in some places incomplete - especially interesting to me was the part that would go after "If precision was something necessary, then we could have a storage of ".
the problem that I've found in the past[1] is that it is impossible to generate fully working configuration just from the bundles itself, specifically bundles start levels are unknown. I believe that for this reason it is necessary to ship either repository metadata, either fragmentary bundles.info (or ship start level info in any other way, but those two seems to be the simplest one). Hence the idea of generating the fragmentary bundles.info during the build (via tycho/maven plugin). As a bonus, we avoid filesystem walkthrough. I'm not sure whether this approach to bundles.info belongs more to droplets, or to the dynamic profile generation. It looks like something in between. The assumption is that master Eclipse will be entirely managed by RPM. As I don't expect anything but the installer to write to the bundles.info in the master configuration, I think there is no need to change any other simpleconfigurator logic than mentioned above. I could implement saveguards to ensure that this path will not be merged until simpleconfigurator is configured with a read-only directory. The change that is required in the simpleconfigurator could be similar to [2] (pretty-old code). As of profiles - I initially thought of generating also a fragmentary profile, that would be merged together on the same basis as bundles.info. The idea was to generate it during build time, and then merge when it would be necessary to access it. On the other hand, shipping profile-less Eclipse just with bundles.info would definitely allow for spoofing the entire profile on-demand. If we have bundles.info (but the proper one, with start-levels), we can easily regenerate the shared profile when necessary. After reading all that what I've written it looks like it is very close to the 'dynamic profile creation' scenario, with a couple of minor differences. [1] http://eclipseandlinux.blogspot.com/2012/02/making-p2-working-with-rpm-milestone-i.html [2] http://fpaste.org/49439/82700200/ -- Krzysztof Daniel <[email protected]> Red Hat _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
