From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 6/9] package/libpjsip: add Asterisk patch set
Date: Sun, 14 Oct 2018 14:46:46 +0200 [thread overview]
Message-ID: <20181014144646.3ad2f867@windsurf> (raw)
In-Reply-To: <20181014090202.31122-6-bernd.kuhls@t-online.de>
Hello,
On Sun, 14 Oct 2018 11:01:58 +0200, Bernd Kuhls wrote:
> Quoting https://wiki.asterisk.org/wiki/display/AST/PJSIP-pjproject
>
> "Asterisk currently contains two SIP stacks: the original chan_sip SIP
> channel driver which is a complete standalone implementation, has been
> present in all previous releases of Asterisk and no longer receives
> core support, and the newer chan_pjsip SIP stack that is based on
> Teluu's "pjproject" SIP stack.
> [...]
> The actual pjproject source code is NOT distributed with Asterisk.
> Instead the Asterisk build process downloads the official pjproject
> tarball then patches, configures and builds pjproject when you build
> Asterisk."
>
> This patch allows to use a buildroot-build libpjsip with all patches,
> except 0000-remove-third-party.patch, provided by Asterisk.
I don't understand the story about 0000-remove-third-party.patch. Could
you explain ? All patches are provided by Asterisk, they are at
https://github.com/asterisk/asterisk/tree/16.0/third-party/pjproject/patches.
One issue with this is that 16.0 is a branch name, so the patches that
you download are not guaranteed to be stable over time.
Also, what is the upstream status of those patches ? Is Asterisk
actively contributing those patches to upstream pjsip, or are they
doing de-facto a fork of it ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-14 12:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 9:01 [Buildroot] [PATCH v3 1/9] DEVELOPERS: add myself for asterisk Bernd Kuhls
2018-10-14 9:01 ` [Buildroot] [PATCH v3 2/9] package/asterisk: libsrtp needs openssl Bernd Kuhls
2018-12-06 22:17 ` Thomas Petazzoni
2018-12-09 21:24 ` Thomas Petazzoni
2018-12-16 20:02 ` Peter Korsgaard
2018-10-14 9:01 ` [Buildroot] [PATCH v3 3/9] package/asterisk: bump version to 16.0.0 Bernd Kuhls
2018-12-09 21:24 ` Thomas Petazzoni
2018-10-14 9:01 ` [Buildroot] [PATCH v3 4/9] package/asterisk: enable for uclibc toolchains Bernd Kuhls
2018-12-09 21:24 ` Thomas Petazzoni
2018-10-14 9:01 ` [Buildroot] [PATCH v3 5/9] package/libpjsip: disable build of test binaries Bernd Kuhls
2018-12-09 21:25 ` Thomas Petazzoni
2018-10-14 9:01 ` [Buildroot] [PATCH v3 6/9] package/libpjsip: add Asterisk patch set Bernd Kuhls
2018-10-14 12:46 ` Thomas Petazzoni [this message]
2018-12-09 21:25 ` Thomas Petazzoni
2018-10-14 9:01 ` [Buildroot] [PATCH v3 7/9] package/libpjsip: add optional dependency to speex Bernd Kuhls
2018-12-09 21:25 ` Thomas Petazzoni
2018-10-14 9:02 ` [Buildroot] [PATCH v3 8/9] package/libpjsip: add optional dependency to libgsm Bernd Kuhls
2018-12-09 21:25 ` Thomas Petazzoni
2018-10-14 9:02 ` [Buildroot] [PATCH v3 9/9] package/asterisk: add optional dependency to libpjsip Bernd Kuhls
2018-12-03 22:10 ` [Buildroot] [PATCH v3 1/9] DEVELOPERS: add myself for asterisk Thomas Petazzoni
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=20181014144646.3ad2f867@windsurf \
--to=thomas.petazzoni@bootlin.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