Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Best way to contribute values (eg PGP keys) with OSGi?


as far as I know P2 supports OSGi Capabilities and Requirements that Tom mentioned.

Mark Hoffmann 
M.A. Dipl.-Betriebswirt (FH) 

Phone: +49 3641 384 910

Data In Motion Consulting GmbH 
Kahlaische Strasse 4 
07745 Jena 

Mark Hoffmann 
Jürgen Albert 

Jena HRB 513025 
Steuernummer 162/107/05779 
USt-Id DE310002614

-------- Ursprüngliche Nachricht --------
Von: Mickael Istria <mistria@xxxxxxxxxx>
Datum: 01.12.21 16:43 (GMT+01:00)
An: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>, P2 developer discussions <p2-dev@xxxxxxxxxxx>
Betreff: [equinox-dev] Best way to contribute values (eg PGP keys) with OSGi?

Hi all,

In the context of , 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 Istria
Eclipse IDE developer, for Red Hat Developers

Back to the top