all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Add murmur.
Date: Fri, 10 Feb 2017 21:39:59 +0000	[thread overview]
Message-ID: <20170210213959.on6psfta6jcbjv2b@wasp> (raw)
In-Reply-To: <87efz7asit.fsf@gnu.org>

On 17-02-09 23:50:02, Ludovic Courtès wrote:
> 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.
>

I don't see my description as aesthetics, but maybe I wasn't clear. It
could theoretically be an security issue, keeping both separated gives
the user a choice of what should be present.

Of course this is a theoretic issue, but the separation of server+client
where applicable when the nature of an application allows it makes sense
to me.

If you don't agree, I can send an updated patch which just adds murmur
to the 'out'.
 
> How does that sound?
> 
> Ludo’.
> 

-- 
ng0 -- https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-02-10 21:38 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
2017-02-10 21:39       ` ng0 [this message]
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=20170210213959.on6psfta6jcbjv2b@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.