[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Packaging Jami progress

From: Jan
Subject: Re: Packaging Jami progress
Date: Thu, 14 Nov 2019 23:16:05 +0100

On Thu, 14 Nov 2019 22:54:15 +0100
Pierre Neidhardt <address@hidden> wrote:

> I don't think it's a Jami bug: as I mentioned the same bug affects the
> old package so I believe it comes from us.
Sorry, didn't read the entire message, I'm a bit tired, because of

> The thing is that those are 3 different build processes, so having 3
> packages makes it easier to package.  I believe what we have is the
> most natural way to go.
Okay then.

> What do you mean?  Guix can be installed on foreign distribution and
> Jami would work there the same way it works on Guix System.
I mean Windows (ReactOS in the future?), OSX, iOS, Android - Jami is an
universal platform. AFAIK there's the option to build with
--target=mingw64 or something like this. Could Guix support other
targets as well? Some people in the Jami community want to have
reproducible builds for Jami, no matter on what distribution. 
Providing reproducible builds for other systems is going to improve
overall security of the platform. 

> It's the job of the init system to decide what to start.  The Guix
> pack does not embed any init system information, I don't know if it
> can or even if that would make sense.

> Wouldn't it be a user service?
I'm not sure if I understand this correctly, but autostart on GNU/Linux
is handled by different init systems/process supervisors. How is the
autostart handled on Guix System? When I searched for the way of adding
a program to autostart on Debian-based distributions, I often found
tutorials showing how to make an init script or systemd-something,
anyway I thought that if libring is a daemon, then there needs to be
something written for the Shepherd, but if it's handled as an user
service, then it's fine.

> I'm not sure there is much more we can do here: regarding the
> packaging process, we already have a tutorial (cf. the cookbook) that
> covers everything needed to package Jami.  (As tough as Jami may be
> to package...)
I found some things hard/unintuitive, but maybe that's because I didn't
entirely read the tutorial. Anyway if I find something worth improving,
I'll tell.

> Regarding the dependencies, it belongs to upstream
> to tell which deps Jami uses; sadly this is not done very well in
> their current documentation.  We could open an issue I suppose.
I'll ask about this.
> Cheers!

Jan Wielkiewicz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]