Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V3 1/1] sngrep: new package
Date: Thu, 26 Jan 2017 21:55:05 +1300	[thread overview]
Message-ID: <20170126215505.1334a8ff@free-electrons.com> (raw)
In-Reply-To: <20170125145446.23466-1-aduskett@codeblue.com>

Hello,

On Wed, 25 Jan 2017 09:54:46 -0500, Adam Duskett wrote:
> sngrep is a tool for displaying SIP calls message flows from terminal.
> It supports live capture to display realtime SIP packets and can also
> be used as PCAP viewer.
> 
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>

I've applied, but after doing quite a few changes:

    [Thomas:
     - ncurses wide char and other sub-options are not needed to build
       sngrep, so they are removed, as well as the wchar
       dependency. ncurses with wchar support is only needed when
       --enable-unicode is passed, but even then, it doesn't work because
       the configure script searches <ncursesw/ncurses.h>, so unicode
       support has been explicitly disabled.
     - add optional dependencies on OpenSSL, GnuTLS and PCRE. This also
       makes sure they are explicitly enabled/disabled depending on the
       configuration.
     - add upstream URL in Config.in file.]

In a follow-up commit, I also added you in the DEVELOPERS file for
python-mutagen and sngrep.

Thanks for your contribution!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2017-01-26  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 14:54 [Buildroot] [V3 1/1] sngrep: new package Adam Duskett
2017-01-26  8:55 ` Thomas Petazzoni [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=20170126215505.1334a8ff@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox