diff options
| author | Patrick McDermott <pehjota> | 2019-04-02 14:59:57 (EDT) |
|---|---|---|
| committer | Patrick McDermott <pehjota> | 2019-04-02 14:59:57 (EDT) |
| commit | 85a73dc3cbd27cd754394a2c537b032dc0b93b18 (patch) | |
| tree | af51354b4f77e1bf1e66b11fd335099af4774ec0 /dev/archive | |
| parent | ff3066d578e0dca9249b05f9724db80132ec866c (diff) | |
dev/archive/signing: opkg can now verify package feeds
Diffstat (limited to 'dev/archive')
| -rw-r--r-- | dev/archive/signing.mdwn | 16 |
1 files changed, 3 insertions, 13 deletions
diff --git a/dev/archive/signing.mdwn b/dev/archive/signing.mdwn index ac512b9..43904bc 100644 --- a/dev/archive/signing.mdwn +++ b/dev/archive/signing.mdwn @@ -63,19 +63,9 @@ Suggestions welcome. Opkg ---- -The opkg package manager supports verifying package feeds. This feature -requires linking against the [GnuPG Made Easy (GPGME) library][gpgme]. - -GPGME and its dependencies are now packaged in ProteanOS, so opkg can be built -with package feed verification. This feature should be optional. The `opkg` -source package should have two builds, with and without verification enabled. -This will probably mean generating new binary packages `opkg-gpg` and -`libopkg.1-gpg` (which will conflict with `opkg` and `libopkg.1` respectively) -and installing data files into binary package directories without the aid of -`oh-installfiles`. Although, option 1 of the [[static_libopkg|pkg/opkg/static]] -plan would simplify this by getting rid of the `libopkg.1` and `libopkg.1-dev` -packages altogether. The `opkg` source package could then build just `opkg`, -`opkg-gpg`, `opkg-dbg`, and `opkg-doc` binary packages. +The opkg source package now builds opkg-gpg and opkg binary packages with and +without support for package feed verification using the [GnuPG Made Easy (GPGME) +library][gpgme] and its dependencies. Archive Keyring --------------- |