From: Marius Bakke <mbakke@fastmail.com>
To: Andreas Enge <andreas@enge.fr>, Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, Hartmut Goebel <h.goebel@goebel-consult.de>
Subject: Re: [PATCH 1/1] gnu: Add acme-client.
Date: Sat, 03 Sep 2016 11:32:20 +0100 [thread overview]
Message-ID: <877fatqnnv.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20160903100413.GA6340@solar>
Andreas Enge <andreas@enge.fr> writes:
> On Fri, Sep 02, 2016 at 02:50:28PM -0400, Leo Famulari wrote:
>> On Fri, Sep 02, 2016 at 08:01:55PM +0200, Hartmut Goebel wrote:
>> > Am 02.09.2016 um 16:49 schrieb Leo Famulari:
>> > > + (name "acme-client")
>> > I strongly suggest using a different name, as this is *one* of many
>> > implementations and it is not the "official" one.
>> Suggestions?
>
> Is there other reasonably widely used software with this name? Our package
> guidelines say to use the upstream name.
I don't know about widely used, but searching "acme-client" on github
shows four projects with this name, neither of which is this package.
Many distros prefix OpenBSD projects with ambigous names with
"openbsd-". E.g. "openbsd-netcat", "openbsd-ntpd" etc. We don't appear
to have that problem yet, but I think this could be a good precedent.
-marius
next prev parent reply other threads:[~2016-09-03 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 14:49 [PATCH 0/1] Another Let's Encrypt client Leo Famulari
2016-09-02 14:49 ` [PATCH 1/1] gnu: Add acme-client Leo Famulari
2016-09-02 18:01 ` Hartmut Goebel
2016-09-02 18:50 ` Leo Famulari
2016-09-02 18:58 ` Leo Famulari
2016-09-03 7:43 ` Hartmut Goebel
2016-09-03 10:04 ` Andreas Enge
2016-09-03 10:32 ` Marius Bakke [this message]
2016-09-04 2:43 ` Leo Famulari
2016-09-04 5:12 ` Marius Bakke
2016-09-04 2:29 ` Leo Famulari
2016-09-11 12:42 ` Andreas Enge
2016-09-11 12:57 ` Hartmut Goebel
2016-09-12 17:06 ` Leo Famulari
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=877fatqnnv.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=h.goebel@goebel-consult.de \
--cc=leo@famulari.name \
/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.