all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>, 41490@debbugs.gnu.org
Subject: [bug#41490] Advice on package naming
Date: Tue, 09 Jun 2020 18:13:00 +0200	[thread overview]
Message-ID: <87o8psgqur.fsf@gnu.org> (raw)
In-Reply-To: <663e709a-31ed-54ef-faa3-67fea9bf5b6e@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 8 Jun 2020 18:06:55 +0200")

Hi Hartmut,

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> 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

That LGTM, I think it’s pretty much in line with:

  https://guix.gnu.org/manual/en/html_node/Package-Naming.html

Thanks,
Ludo’.




  reply	other threads:[~2020-06-09 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 18:48 [bug#41490] [PATCH 0/5] Add pEp (pretty Easy privacy) Hartmut Goebel
2020-05-23 18:51 ` [bug#41490] [PATCH 1/5] gnu: Add yml2 Hartmut Goebel
2020-05-23 18:51 ` [bug#41490] [PATCH 2/5] gnu: Add pep-engine Hartmut Goebel
2020-05-23 18:51 ` [bug#41490] [PATCH 3/5] gnu: Add libpepadapter Hartmut Goebel
2020-05-23 18:51 ` [bug#41490] [PATCH 4/5] gnu: Add python-pep-adapter Hartmut Goebel
2020-05-23 18:51 ` [bug#41490] [PATCH 5/5] gnu: Add java-pep-adapter Hartmut Goebel
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
2020-06-09 16:13   ` Ludovic Courtès [this message]
2020-06-09 18:02     ` bug#41490: Advice on package naming Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8psgqur.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41490@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.