Re: Maintaining GNU Jami package for Guix

[Pierre Neidhardt <mail@ambrevar.xyz>]

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

Jan <tona_kosmicznego_smiecia@interia.pl> writes:

> On Sat, 19 Oct 2019 22:52:58 +0200
> Ricardo Wurmus <rekado@elephly.net> 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 :)

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 upstream.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]