Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] pjsip package status
Date: Mon, 22 Feb 2016 23:33:44 +0100	[thread overview]
Message-ID: <20160222223344.GA3463@free.fr> (raw)
In-Reply-To: <841623823.459573.1456179714125.JavaMail.zimbra@savoirfairelinux.com>

Patrick, All,

On 2016-02-22 17:21 -0500, Patrick Keroulas spake thusly:
> Sure I can take a look at this but my BR experience is quite limited.
> Not sure about gsm, srtp, and portaudio. Why aren't they treated like
> other options?  Are you sure they're necessary for Asterisk application?

Well, I was mostly pointing you to this branch so you can look at the
pjsip package (since that was your inquiry).

I am not sure what you meant by "treated like other options". Some of
the features in Asterisk have dependencies on other packages (like srtp
for example), while others use internal code (like gsm for example).

No, they are not _strictly_ required for Asterisk to behave. Asterisk
can be an IP-only application, but it can also make use of telephony
cards (hence ss7 et al.). It seems it can also understand some GSM
dialect, too. But all that is optional and depends on what the user
needs; so some users may enable some of those options, while other users
may enable some other options.

> I thought configure options should limit the package footprint as much
> as possible.

Well, you could put it that way. I prefer to say:
    We have options so only what is strictly needed is present.

Which incidentally reduces the footprint! ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-02-22 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 20:04 [Buildroot] pjsip package status Patrick Keroulas
2016-02-17 21:05 ` Thomas Petazzoni
2016-02-20 17:35 ` Yann E. MORIN
2016-02-22 22:21   ` Patrick Keroulas
2016-02-22 22:33     ` Yann E. MORIN [this message]
2016-02-23 16:53     ` Luca Ceresoli

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=20160222223344.GA3463@free.fr \
    --to=yann.morin.1998@free.fr \
    --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