From: ng0 <contact.ng0@cryptolab.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, guix-devel@gnu.org
Subject: Re: [PATCH 6/6] gnu: Add postorius.
Date: Mon, 30 Jan 2017 10:12:24 +0000 [thread overview]
Message-ID: <87y3xsrh4n.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <588F0577.7090908@crazy-compilers.com>
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Hi,
>
> Am 30.01.2017 um 10:10 schrieb ng0:
>>
>>>> + (file-name (string-append name "-" version ".tar.gz"))
>>> I'd keep the original name, but this may be a matter of taste.
>> The original file name has some "+something2.tar.gz" in it, I want
>> to be consistent with what we provide.
>> Or what do you mean?
>
> I suggest keeping te original filename. But I don't know the exacpt
> conventions at Guix for this.
Basically one part says: No strange characters, versions only
separated with dots, etc. Which is why I removed the
"+foo2.tar.gz".
But as you said, it's (almost) purely cosmetical.
>> Thanks, I will apply this. They should fix their pypi source (if I got
>> it from there).
>
> ACK.
>
>>>> + (synopsis "Web user interface for GNU Mailman")
>>> Mention "Mailman 3"?
>> We only "have" version 3, why should I mention a version then? I
>> can do it... Did Mailman prior to version 3 have different
>> frontends than version 3?
>
> Mailman 3 is a completely new product. AFAIK most part are re-developed
> from scratch. OTOH at http://list.org/ they are just mentioning
> "Mailman" and "versions are 2.1.23 … and 3.0.3 …". An at mailman-bundler
> [1] they write "This is GNU Mailman" and "This package installs GNU
> Mailman".
>
> So probably we should stay with what you did: just call ist "Mailman".
>
> [1] https://pypi.python.org/pypi/mailman-bundler/3.0.0
Thanks. I would say calling it Mailman 3 makes sense if for
example someone decides mailman-4 comes out but we need to keep
mailman-3 around. The version number found through either of
"guix package {--show,--search} $some-mailman-related package"
will be enough in my opinion.
We should definitely mention Mailman *3* in the documentation for
the service we eventually will write.
>>
>>> Please move it down to the description - I overlooked it first.
>> I assume you mean the "Web user interface for GNU Mailman 3".
>> In case I haven't mentioned it there, I will do so, okay.
>
> I meant the "synopsis" entry which I expect to be beside the description
> and not separate.
Okay, thanks.
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel | h.goebel@crazy-compilers.com |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
--
ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-30 10:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 23:26 Mailman3 frontend number one: postorius contact.ng0
2017-01-29 23:26 ` [PATCH 1/6] gnu: Add python-defusedxml contact.ng0
2017-01-29 23:26 ` [PATCH 2/6] gnu: Add python-openid contact.ng0
2017-01-29 23:26 ` [PATCH 3/6] gnu: Add python-django-allauth contact.ng0
2017-01-29 23:26 ` [PATCH 4/6] gnu: Add python-django-gravatar2 contact.ng0
2017-01-29 23:26 ` [PATCH 5/6] gnu: Add python-django-mailman3 contact.ng0
2017-01-29 23:26 ` [PATCH 6/6] gnu: Add postorius contact.ng0
2017-01-30 8:48 ` Hartmut Goebel
2017-01-30 9:10 ` ng0
2017-01-30 9:20 ` Hartmut Goebel
2017-01-30 10:12 ` ng0 [this message]
2017-01-29 23:31 ` Mailman3 frontend number one: postorius ng0
2017-01-30 11:22 ` postorius, v2 contact.ng0
2017-01-30 11:22 ` [PATCH 1/6] gnu: Add python-defusedxml contact.ng0
2017-01-30 11:22 ` [PATCH 2/6] gnu: Add python-openid contact.ng0
2017-01-30 11:22 ` [PATCH 3/6] gnu: Add python-django-allauth contact.ng0
2017-01-30 11:22 ` [PATCH 4/6] gnu: Add python-django-gravatar2 contact.ng0
2017-01-30 11:22 ` [PATCH 5/6] gnu: Add python-django-mailman3 contact.ng0
2017-01-30 11:22 ` [PATCH 6/6] gnu: Add postorius contact.ng0
2017-01-31 13:40 ` postorius, v2 Hartmut Goebel
2017-02-02 11:51 ` Hartmut Goebel
2017-02-02 12:13 ` ng0
2017-02-02 12:28 ` Python packaging rules again (was: postorius, v2) Hartmut Goebel
2017-02-02 21:28 ` postorius, v2 ng0
2017-02-05 1:28 ` ng0
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=87y3xsrh4n.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--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.