From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>, 41490@debbugs.gnu.org
Subject: Advice on package naming (was: [PATCH 0/5] Add pEp (pretty Easy privacy))
Date: Mon, 8 Jun 2020 18:06:55 +0200 [thread overview]
Message-ID: <663e709a-31ed-54ef-faa3-67fea9bf5b6e@crazy-compilers.com> (raw)
In-Reply-To: <cover.1590259641.git.h.goebel@crazy-compilers.com>
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 |
prev parent reply other threads:[~2020-06-08 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=663e709a-31ed-54ef-faa3-67fea9bf5b6e@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=41490@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).