all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add wireshark
Date: Sat, 04 Jun 2016 23:55:32 +0200	[thread overview]
Message-ID: <87a8j0wre3.fsf@gnu.org> (raw)
In-Reply-To: <87zir35p5d.fsf@saiph.selenimh> (Nicolas Goaziou's message of "Thu, 02 Jun 2016 22:09:18 +0200")

Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:

> Here is a new attempt to add a package: wireshark.
>
> I don't like the "python-wrapper" part because it implies a propagated
> python. OTOH, providing only "python" generates a lot of screaming
> during patch environment phase, but doesn't seem to alter the final
> executable.

Right, it’s not listed in ‘guix gc --references’, so that’s fine.

> I'm not sure about the locations of plugins directory. Default is in the
> store, which means you cannot add more. I don't use this, so I don't
> know if there's a better place.

I guess we can revisit it later when someone needs a plugin.

> From e31d8434e26100bc95e2c7fa8a98dafcb4b49c45 Mon Sep 17 00:00:00 2001
> From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Thu, 2 Jun 2016 21:02:14 +0200
> Subject: [PATCH] gnu: Add wireshark.
>
> * gnu/packages/networking.scm (wireshark): New variable.

Applied with minor changes:

> +       `(,(string-append "--with-c-ares=" (assoc-ref %build-inputs "c-ares"))
> +         ,(string-append "--with-krb5=" (assoc-ref %build-inputs "krb5"))

I changed it to (list (string-append …) …), which I find more readable.

> +\"packet sniffer\", that lets you capture and interactively browse the
   ^

I changed it to @dfn{packet sniffer}.

Thank you!

Ludo’.

      reply	other threads:[~2016-06-04 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 20:09 [PATCH] Add wireshark Nicolas Goaziou
2016-06-04 21:55 ` Ludovic Courtès [this message]

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=87a8j0wre3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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.