From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Maintaining GNU Jami package for Guix Date: Sun, 03 Nov 2019 17:37:10 +0100 Message-ID: <878sowq5l5.fsf@devup.no> References: <20191018205608.45b264dc@kompiuter> <20191031211919.175c3f29@interia.pl> <87bltwpn4w.fsf@devup.no> <20191101130139.6193f6df@interia.pl> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50404) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRIsP-00027X-MG for guix-devel@gnu.org; Sun, 03 Nov 2019 11:37:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRIsM-0008Oc-7v for guix-devel@gnu.org; Sun, 03 Nov 2019 11:37:17 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:40683) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iRIsL-0008Nm-Nz for guix-devel@gnu.org; Sun, 03 Nov 2019 11:37:14 -0500 In-Reply-To: <20191101130139.6193f6df@interia.pl> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jan Wielkiewicz Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Jan Wielkiewicz writes: > Dnia 2019-10-31, o godz. 23:26:39 > Marius Bakke napisa=C5=82(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/ I did not find any cURL or GnuTLS patches there. Maybe I misunderstood something? >> 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.=20 > >> If they really need special patched versions of some libraries, you >> can do something along these lines to create a >> cusctm variant: >>=20 >> (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=20 > gnutls @ 3.6.7, gnutls @ 3.6.9 etc?=20=20=20 Both GnuTLS and cURL have stable ABIs. That means, a package linked against cURL 7.63 will almost certainly work with cURL 7.66 without changes (even without recompilation). There are many reasons not to include multiple versions of a package, but for cURL and GnuTLS in particular, the main reason is that there are security fixes in nearly every new version. Thus, we can only support the latest one. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2/AjYACgkQoqBt8qM6 VPrLEwgAi4a0g+vUbwUStrYlOhu05FJbnZyRQWmiOZrf0IhFc9dgHVFwP/F+OiF5 B2hmZNJGN8Q4z4DcQ7gVZJhwjZXf0L/xJq/iTYQygPY1+JjO8XsYXRg8/ddm2B/3 EPdHKXKlfhTTw19cY0MM7ZMGN+MwYLRc6XyY3rFZOTwz/KElKIH7gk/3mMNwyOA1 jITPFXU66iZuStmorQ2fkADF4PkRKY8OGCBwM9npLeEXvAFVPgvNk1dARAgt05IY yV5BN7FQgMMVHNkAO5NoPXLDcskjb9/SDHQwH/Sc64KlW2YOmCjwA12/32quJzew qhnw+gh57oZn5hxY4btUCJKGYOQEKw== =HHKL -----END PGP SIGNATURE----- --=-=-=--