all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Fri, 1 Nov 2019 13:01:39 +0100	[thread overview]
Message-ID: <20191101130139.6193f6df@interia.pl> (raw)
In-Reply-To: <87bltwpn4w.fsf@devup.no>

Dnia 2019-10-31, o godz. 23:26:39
Marius Bakke <mbakke@fastmail.com> napisał(a):

> Do you have a link to the patches that Jami/pjproject needs?
You can find patches in the ring-project/daemon/contrib/src/pjproject
directory from the latest source tarball here:
https://dl.jami.net/ring-release/tarballs/

> It would be great if we could use system versions of GnuTLS and cURL,
> because otherwise Jami risks not getting security updates.
A bit unlikely, they update dependencies quickly, but they're slower
than upstream. Keeping a separate version and updating it paralelly
will prevent breaking the build process of the modified pjproject
version. 

> If they really need special patched versions of some libraries, you
> can do something along these lines to create a
> cusctm 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"))))))))
Why can't we just keep paralell version for a package? Like 
gnutls @ 3.6.7, gnutls @ 3.6.9 etc?   

> I realize now that this won't do the right thing wrt grafts, but we
> can deal with that later.  :-)
Don't really know what grafts are yet, so we can indeed skip this
now :)


Jan Wielkiewicz

  reply	other threads:[~2019-11-01 12:01 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
2019-11-01 12:01     ` Jan Wielkiewicz [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191101130139.6193f6df@interia.pl \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.