From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Packaging pjproject
Date: Fri, 31 Jan 2020 17:27:45 +0100 [thread overview]
Message-ID: <20200131172745.7d12ab53@kompiuter> (raw)
In-Reply-To: <87sgjvmx13.fsf@devup.no>
On Fri, 31 Jan 2020 17:05:28 +0100
Marius Bakke <mbakke@fastmail.com> wrote:
>
> Unfortunately there is no single approach for dealing with these kinds
> of problems, as they are typically highly package-specific.
Do I have to learn GNU Make to be able to deal with it?
> I must admit that I'm a little confused between pjproject and
> pjproject-jami. Is it correct to assume that the latter exists only
> because the former fails to build? Why are you trying to switch?
Both pjproject and pjproject-jami are Pierre's work.
pjproject is unmodified, but never worked, while pjproject-jami is
pjproject with Savoir-faire Linux patches - they introduce some serious
modifications, which are usable only for Jami. That's why
pjproject-jami exists. pjproject-jami works only because configure
flags disable unused dependencies, yet somehow our Jami package crashes
because of something connected to pjproject.
https://git.jami.net/savoirfairelinux/jami-packaging/issues/63
> Would it make sense to get rid of pjproject entirely (nothing depends
> on it) in favor of pjproject-jami?
We could do it, but why do so, if most of the work has been done? Guix
System is incremental work and even if nothing needs pjproject now, it
could be useful for someone in the future. It just needs to be fixed.
Jan Wielkiewicz
next prev parent reply other threads:[~2020-01-31 16:28 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 [this message]
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
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=20200131172745.7d12ab53@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).