mbox

[bug#41490,0/5] Add pEp (pretty Easy privacy)

Message ID cover.1590259641.git.h.goebel@crazy-compilers.com
Headers show

Message

Hartmut Goebel May 23, 2020, 6:48 p.m. UTC 
This adds the build tools and libraries for pretty Easy Privacy, a library for
automatic key management and encryption of messages.

How shall we name the packages here?
I'd appreciate feedback to the package names, since the original packages have
quiet uncommon names:

- pEpEngine -> pep-engine (main library)
- libpEpAdapter -> intermediate layer library
- pEpPythonAdapter -> python-pep-adapter
- pEpJNIAdapter -> java-pep-adapter

The project as other packages like these:
- pEpQtAdapter
- pEpJSONServerAdapter
- pEpObjCAdapter

In Arch Linux AUR packages are named pep-engine, libpep-adapter,
python-pep-adapter, pep-jni-adapter, pep-qt-adapter.

Hartmut Goebel (5):
  gnu: Add yml2.
  gnu: Add pep-engine.
  gnu: Add libpepadapter.
  gnu: Add python-pep-adapter.
  gnu: Add java-pep-adapter.

 gnu/local.mk         |   1 +
 gnu/packages/pep.scm | 349 +++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 350 insertions(+)
 create mode 100644 gnu/packages/pep.scm

Comments

Hartmut Goebel June 7, 2020, 10:09 a.m. UTC | #1 
Hi Guix,

I'm still seeking advice on how to name these packages. Shall I keep the
names I'm currently using, or are there any other suggestions?

Am 23.05.20 um 20:48 schrieb Hartmut Goebel:
> This adds the build tools and libraries for pretty Easy Privacy, a library for
> automatic key management and encryption of messages.
>
> How shall we name the packages here?
> I'd appreciate feedback to the package names, since the original packages have
> quiet uncommon names:
>
> - pEpEngine -> pep-engine (main library)
> - libpEpAdapter -> intermediate layer library
> - pEpPythonAdapter -> python-pep-adapter
> - pEpJNIAdapter -> java-pep-adapter
>
> The project as other packages like these:
> - pEpQtAdapter
> - pEpJSONServerAdapter
> - pEpObjCAdapter
>
> In Arch Linux AUR packages are named pep-engine, libpep-adapter,
> python-pep-adapter, pep-jni-adapter, pep-qt-adapter.
Hartmut Goebel June 8, 2020, 4:06 p.m. UTC | #2 
Hi Guix,

I'm still seeking advice on how to name these packages, since the
original packages have
quiet uncommon names. Shall I keep the names I'm currently using, or are
there any other suggestions?

Current names:

pep-engine
libpepadapter.
python-pep-adapter
java-pep-adapter

Am 23.05.20 um 20:48 schrieb Hartmut Goebel:
> How shall we name the packages here?
> I'd appreciate feedback to the package names, since the original packages have
> quiet uncommon names:
>
> - pEpEngine -> pep-engine (main library)
> - libpEpAdapter -> intermediate layer library
> - pEpPythonAdapter -> python-pep-adapter
> - pEpJNIAdapter -> java-pep-adapter
>
> The project as other packages like these:
> - pEpQtAdapter
> - pEpJSONServerAdapter
> - pEpObjCAdapter
>
> In Arch Linux AUR packages are named pep-engine, libpep-adapter,
> python-pep-adapter, pep-jni-adapter, pep-qt-adapter.