From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Maintaining GNU Jami package for Guix Date: Sun, 20 Oct 2019 13:51:19 +0200 Message-ID: <877e4zd494.fsf@ambrevar.xyz> References: <20191018205608.45b264dc@kompiuter> <87ftjpyhsz.fsf@devup.no> <87mudxhzv8.fsf@ambrevar.xyz> <20191019223821.71b6dd45@interia.pl> <87sgnojw4f.fsf@elephly.net> <20191020003719.291dcf2c@kompiuter> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38628) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iM9k4-0007uj-OP for guix-devel@gnu.org; Sun, 20 Oct 2019 07:51:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iM9k2-0002zZ-EO for guix-devel@gnu.org; Sun, 20 Oct 2019 07:51:24 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:39569) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iM9k2-0002zA-0L for guix-devel@gnu.org; Sun, 20 Oct 2019 07:51:22 -0400 In-Reply-To: <20191020003719.291dcf2c@kompiuter> 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 , Ricardo Wurmus Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Jan writes: > On Sat, 19 Oct 2019 22:52:58 +0200 > Ricardo Wurmus wrote: > >> We always try to unbundle libraries, because that ensures that all >> packages benefit from security fixes. >>=20 > > Great, so I have to package everything recursively :) You'll only have to package they new dependencies they've introduced since I last packaged Jami, if any. It should not be more than 1 or 2 I guess. Maybe 0. > Just to make it clear, because I'm a bit unfamiliar with build systems > and the package API - will packing every library pjproject uses and > just adding it in the "inputs" field make building possible, or will I > have to do magic and copy built packages into "third_party" folder in > the pjproject source tree? This is already taken care of in the last version of Jami. > Also what if pjproject (or any package I want to update) depends on a > specific version of a library? Should I just update the package, or > should I add a separate version of the library? You can always define a non-exported package to a specific version if Jami needs that. In the current version of Jami, if I recall correctly, only pjproject needed a forked version, everything else was following upstr= eam. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl2sSjcACgkQm9z0l6S7 zH+1lQgAgz+stP3oV/4PXgI/Rld4q+p+GfPE5nS2Ko0fepI8/YGC+OqM6QP60F6p uuzWNmpBl3SOt4MsJXlsAH46KAoLhEiOdxTa0IDZvA9q6VT9bkHJumetK5qPK4ns z0BQBQx/BcOAqBOqLYhuE8CgCz77BEZ/SARLf3n5ziys0BmakZb24uOdqh5jI4ng gn5wvMSTH1Byxlf7QUAq6qQwGKXtKJimknsUP1Zxo2WI2CGN1gSeFZ7Btjluarqc iDicXoUPn5kg360D4Mjvq/6ZwBbDiAL9IkvbCm20UQGNoeKB2ssVZLYcC5hv0txV KaOGIFODNgpf3xHoHN6sd9p/pfLJIw== =Yt3U -----END PGP SIGNATURE----- --=-=-=--