From: Marius Bakke <mbakke@fastmail.com>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>,
guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Thu, 31 Oct 2019 23:26:39 +0100 [thread overview]
Message-ID: <87bltwpn4w.fsf@devup.no> (raw)
In-Reply-To: <20191031211919.175c3f29@interia.pl>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl> writes:
> Also as for packaging Jami generally, I think we should keep a separate
> versions of things like gnutls and pjproject (basically all
> dependencies of pjproject), because version used by Jami are often not
> up to date and considering patches getting applied, using an unproper
> version can break compilation.
Do you have a link to the patches that Jami/pjproject needs?
It would be great if we could use system versions of GnuTLS and cURL,
because otherwise Jami risks not getting security updates.
If they really need special patched versions of some libraries, you can
do something along these lines to create a custom variant:
(define-public gnutls/jami
(hidden-package
(package/inherit
gnutls
(source (origin
(inherit (package-source gnutls))
(patches (append (origin-patches gnutls)
(search-patches "gnutls-jami.patch"))))))))
I realize now that this won't do the right thing wrt grafts, but we can
deal with that later. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-31 22:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 18:56 Maintaining GNU Jami package for Guix Jan
2019-10-18 19:28 ` Marius Bakke
2019-10-19 9:02 ` Pierre Neidhardt
2019-10-19 20:38 ` Jan Wielkiewicz
2019-10-19 20:52 ` Ricardo Wurmus
2019-10-19 22:37 ` Jan
2019-10-20 11:14 ` Ricardo Wurmus
2019-10-20 11:51 ` Pierre Neidhardt
2019-10-20 11:48 ` Pierre Neidhardt
2019-10-25 15:03 ` Pierre Neidhardt
2019-10-25 19:44 ` Jan Wielkiewicz
2019-10-26 10:12 ` Pierre Neidhardt
2019-10-26 23:24 ` Jan Wielkiewicz
2019-10-28 7:53 ` Pierre Neidhardt
2019-10-27 18:13 ` Jan Wielkiewicz
2019-10-27 18:18 ` Pierre Neidhardt
2019-10-27 19:23 ` Jan Wielkiewicz
2019-10-27 21:52 ` Jan Wielkiewicz
2019-10-31 20:19 ` Jan Wielkiewicz
2019-10-31 21:37 ` Pierre Neidhardt
2019-10-31 22:26 ` Marius Bakke [this message]
2019-11-01 12:01 ` Jan Wielkiewicz
2019-11-01 19:02 ` Pierre Neidhardt
2019-11-01 20:42 ` Jan Wielkiewicz
2019-11-02 9:38 ` Pierre Neidhardt
2019-11-03 16:37 ` Marius Bakke
2019-11-03 17:43 ` Jan
2019-11-03 18:06 ` Marius Bakke
2019-11-01 12:29 ` Jan Wielkiewicz
2019-11-01 19:01 ` Pierre Neidhardt
2019-11-01 23:16 ` Jan Wielkiewicz
2019-11-03 10:15 ` Pierre Neidhardt
2019-11-03 10:54 ` Jan Wielkiewicz
2019-11-04 10:02 ` Gábor Boskovits
2019-11-03 10:59 ` Jan Wielkiewicz
2019-11-03 17:07 ` Marius Bakke
2019-11-03 17:47 ` Jan
2019-11-03 18:12 ` Marius Bakke
2019-11-03 18:27 ` Jan
2019-11-03 18:52 ` Marius Bakke
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=87bltwpn4w.fsf@devup.no \
--to=mbakke@fastmail.com \
--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).