all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: Add murmur.
Date: Thu, 09 Feb 2017 23:50:02 +0100	[thread overview]
Message-ID: <87efz7asit.fsf@gnu.org> (raw)
In-Reply-To: <20170209182030.ngn2dsdfbzsmymdj@wasp> (ng0's message of "Thu, 9 Feb 2017 18:20:30 +0000")

ng0 <contact.ng0@cryptolab.net> skribis:

> On 17-02-09 17:50:04, Ludovic Courtès wrote:
>> Hi ng0!
>> 
>> contact.ng0@cryptolab.net skribis:
>> 
>> > This patch adds an proposed change to mumble, murmur as an output.
>> 
>> I’m reluctant to “non-standard” outputs like this.  The reason for
>> multiple outputs should be to reduce the closure size for standards
>> uses.  What do we gain by not included murmurd in “out” in this case?
>> 
>> Thanks,
>> Ludo’.
>
> We remove the server component (murmurd) from the client component
> (mumble).  I imagine that if you run murmurd, you will not want mumble
> in the same user profile.  And if you run mumble, you probably don't
> want murmurd.  The default is a client, adding murmur output is logical.
> But this is just my view.. I would not want a server unless I explicitly
> expressed my intention to have it
>
> What do you think?

I think the only reason to separate things usually is size, not
“aesthetics.”  So I’d be in favor of keeping both in the same output if
there’s no size problem.

How does that sound?

Ludo’.

  reply	other threads:[~2017-02-09 22:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:43 Add murmur contact.ng0
2017-02-01 20:43 ` [PATCH] gnu: mumble: Add 'murmur' output contact.ng0
2017-02-01 21:15 ` Add murmur ng0
2017-02-09 16:50 ` Ludovic Courtès
2017-02-09 18:20   ` ng0
2017-02-09 22:50     ` Ludovic Courtès [this message]
2017-02-10 21:39       ` ng0
2017-02-10 21:54         ` Marius Bakke
2017-02-10 22:15           ` ng0
2017-02-11 14:31             ` Ludovic Courtès
2017-02-11 14:39               ` ng0
2017-02-12 13:37                 ` Ludovic Courtès
2017-02-12 13:53                   ` ng0
2017-02-12 13:57                     ` David Craven
2017-02-12 14:02                       ` ng0
2017-02-12 14:37                         ` David Craven
2017-02-12 17:01                           ` Hartmut Goebel
2017-02-12 17:42                             ` pelzflorian (Florian Pelz)
2017-02-13 14:15                               ` Ludovic Courtès
2017-02-12 17:54                             ` David Craven
2017-02-14 10:13                               ` Hartmut Goebel
2017-02-14  9:00                   ` ng0
2017-02-12 12:23       ` server and client in one package -> security issue (was: Add murmur) Hartmut Goebel
2017-02-12 12:31         ` ng0
2017-02-12 12:53           ` David Craven
2017-02-12 16:52             ` server and client in one package -> security issue Hartmut Goebel
2017-02-13 14:13         ` Ludovic Courtès
2017-02-14 10:28           ` Hartmut Goebel
2017-02-14 11:19             ` Andy Wingo
2017-02-14  9:16         ` server and client in one package -> security issue (was: Add murmur) Danny Milosavljevic
2017-02-14  9:51           ` ng0
2017-02-14 10:44           ` server and client in one package -> security issue Hartmut Goebel
2017-04-24  7:01             ` Maxim Cournoyer

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=87efz7asit.fsf@gnu.org \
    --to=ludo@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 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.