From: Efraim Flashner <efraim@flashner.co.il>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Packaging pjproject
Date: Sun, 2 Feb 2020 20:42:49 +0200 [thread overview]
Message-ID: <20200202184249.GG9517@E5400> (raw)
In-Reply-To: <20200131203445.07a72436@interia.pl>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On Fri, Jan 31, 2020 at 08:35:00PM +0100, Jan Wielkiewicz wrote:
> Dnia 2020-01-31, o godz. 18:12:07
> Pierre Neidhardt <mail@ambrevar.xyz> napisał(a):
>
> > To be more specific, I have never touched pjproject.
> Sorry, didn't know that.
> > I was the 4th person so work on the Jami patch and I fixed pjproject-jami.
> > I sadly have no experience with pjproject beyond that.
> Now thats scary :D
> pjproject is a ghost package.
>
> I can try nagging people on pjproject mailing list, but don't know, if
> I'm up to the task. What should I ask them? "How to build pjproject
> without running make dep" or "Can I build pjproject using system
> libraries"? Should I learn more about build systems to be able to fix
> this, or is it implementation-dependent? My experience with packaging
> so far tells me there is no standard for build systems and every
> package is different.
Debian does a lot of work with unbundling software, I'd check with them
first if they've patched anything to make it work.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-02 18:43 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 [this message]
2020-02-02 22:27 ` Jan
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=20200202184249.GG9517@E5400 \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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).