unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Re: [PATCH 0/5] Add pEp (pretty Easy privacy)
       [not found] <cover.1590259641.git.h.goebel@crazy-compilers.com>
@ 2020-06-07 10:09 ` Hartmut Goebel
  2020-06-08 16:06 ` Advice on package naming (was: [PATCH 0/5] Add pEp (pretty Easy privacy)) Hartmut Goebel
  1 sibling, 0 replies; 2+ messages in thread
From: Hartmut Goebel @ 2020-06-07 10:09 UTC (permalink / raw)
  To: Guix-devel, 41490

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.


-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Advice on package naming (was: [PATCH 0/5] Add pEp (pretty Easy privacy))
       [not found] <cover.1590259641.git.h.goebel@crazy-compilers.com>
  2020-06-07 10:09 ` [PATCH 0/5] Add pEp (pretty Easy privacy) Hartmut Goebel
@ 2020-06-08 16:06 ` Hartmut Goebel
  1 sibling, 0 replies; 2+ messages in thread
From: Hartmut Goebel @ 2020-06-08 16:06 UTC (permalink / raw)
  To: Guix-devel, 41490

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.


-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-06-08 16:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <cover.1590259641.git.h.goebel@crazy-compilers.com>
2020-06-07 10:09 ` [PATCH 0/5] Add pEp (pretty Easy privacy) Hartmut Goebel
2020-06-08 16:06 ` Advice on package naming (was: [PATCH 0/5] Add pEp (pretty Easy privacy)) Hartmut Goebel

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).