|Re: [equinox-dev] Best way to contribute values (eg PGP keys) with OSGi?
> p2 doesn't define extension points, but uses OSGi Services;by the way: Technically P2 does not uses OSGi directly but IProvisioningAgent that supplies services that could be acquired through IProvisioningAgentProvider service.
So maybe it would be good to first define the PGPService or something to make more clear what is required/desired here, e.g. do we need to take minimum mean shortest distance (MSD) into account and such.
Am 01.12.21 um 16:42 schrieb Mickael Istria:
Hi all,In the context of https://bugs.eclipse.org/bugs/show_bug.cgi?id=577248 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=577248> , we need a way for bundles (that were preliminary approved by user) to be capable of contributing some PGP public keys as being "trusted by default". I'm wondering what would be the best way to contribute such extensibility in p2. p2 doesn't define extension points, but uses OSGi Services; but here we only want to contribute a value (that could be the armoured keys, or a path to a resource in the bundle containing such keys...). As far as I am aware -ie not much-, I see 3 possible approaches:1. Define a service interface and let bundles contribute extensions to this interface, eg via OSGI-INF/component.xml* Requires to create 1 service/API interace* Would consuming the service from a bundle automatically trigger bundle activation? That would be undesired.2. Add support for a custom MANIFEST header, something like `Eclipse-P2-PGP-TrustedKey`.* Seems a bit alien, would require some support in tools Are there other solutions you think could fit? What should be preferred? Thanks in advance -- Mickael IstriaEclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat Developers <https://developers.redhat.com/>_______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/equinox-dev
Back to the top