From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Packaging pjproject
Date: Sun, 2 Feb 2020 23:27:26 +0100 [thread overview]
Message-ID: <20200202232727.51ef91f1@kompiuter> (raw)
In-Reply-To: <20200202184249.GG9517@E5400>
On Sun, 2 Feb 2020 20:42:49 +0200
Efraim Flashner <efraim@flashner.co.il> wrote:
>
> Debian does a lot of work with unbundling software, I'd check with
> them first if they've patched anything to make it work.
>
Checked Debian and it doesn't look good.
They removed pjproject from Buster.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925263
"- pjsip is a library where a lot of functionality and behaviour is
selected at compile time using #define statements. Most of these
define statements alter the ABI due to changing structs, which makes
it ill-suited as a system wide library to be used by several programs.
- Consequently, src:ring (now called jami) has always been built
against an embedded copy and src:asterisk also switched to an
embedded copy, both tailored to their needs. There are no other
source packages depending on src:pjproject left"
I picked the worst thing to maintain, didn't I :D
I guess we can remove pjproject then and use only pjproject-jami, but
that doesn't fix the bug. I'll try checking how is pjproject-jami
different from what Jami devs build, but have no clue whatsoever.
Jan Wielkiewicz
next prev parent reply other threads:[~2020-02-02 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:48 Packaging pjproject Jan
2020-01-31 16:05 ` Marius Bakke
2020-01-31 16:27 ` Jan
2020-01-31 17:12 ` Pierre Neidhardt
2020-01-31 19:35 ` Jan Wielkiewicz
2020-02-02 18:42 ` Efraim Flashner
2020-02-02 22:27 ` Jan [this message]
2020-02-02 22:38 ` Jan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200202232727.51ef91f1@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).