From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Maintaining GNU Jami package for Guix Date: Sun, 20 Oct 2019 13:14:16 +0200 Message-ID: <87imojk6t3.fsf@elephly.net> 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: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:35936) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iM9AI-0004fo-0S for guix-devel@gnu.org; Sun, 20 Oct 2019 07:14:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iM9AF-0003bP-2r for guix-devel@gnu.org; Sun, 20 Oct 2019 07:14:25 -0400 Received: from sender4-of-o58.zoho.com ([136.143.188.58]:21859) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iM9AD-0003ar-TX for guix-devel@gnu.org; Sun, 20 Oct 2019 07:14:23 -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 Cc: guix-devel@gnu.org Hi Jan, > 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. >> > > Great, so I have to package everything recursively :) > 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 depends very much on how friendly the build system used by pjproject is. Some applications=E2=80=99 build systems resist any attempts= to request the application to be linked with existing libraries, whereas others will only fall back to the bundled libraries if the libraries don=E2=80=99t already exist somewhere on LIBRARY_PATH. This is why it=E2=80=99s often a big headache to package software that uses custom build systems, as they often lack sane mechanisms for library discovery or overriding. > 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? Let=E2=80=99s discuss this when the need actually arises. We have a few instances of packages that are named =E2=80=9C=E2=80=A6-for-some-other-pack= age=E2=80=9D, but let=E2=80=99s not add them when they aren=E2=80=99t absolutely necessary. -- Ricardo