From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Subject: Re: Packaging Jami progress Date: Thu, 14 Nov 2019 21:40:10 +0100 Message-ID: <20191114214010.7b61005f@kompiuter> References: <20191104214754.793ec2ff@interia.pl> <20191105175001.389c6117@interia.pl> <87pni5qouc.fsf@ambrevar.xyz> <20191106172445.3bdd057d@interia.pl> <87r22lorwh.fsf@ambrevar.xyz> <877e4bo646.fsf@ambrevar.xyz> <20191107204757.23dd08de@interia.pl> <874kzfo21r.fsf@ambrevar.xyz> <20191108192542.5daa7a0a@interia.pl> <87zhh2kdt2.fsf@ambrevar.xyz> <20191111111423.66ec31d5@interia.pl> <87r22ek7x4.fsf@ambrevar.xyz> <874kzajvy9.fsf@ambrevar.xyz> <20191111163843.0629ef41@kompiuter> <87o8xe4d5m.fsf@ambrevar.xyz> <87eeya49hf.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41938) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVLut-0007zn-9o for guix-devel@gnu.org; Thu, 14 Nov 2019 15:40:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iVLur-0007Dd-Tb for guix-devel@gnu.org; Thu, 14 Nov 2019 15:40:35 -0500 Received: from smtpo.poczta.interia.pl ([217.74.65.233]:47051) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iVLur-0006pp-Ao for guix-devel@gnu.org; Thu, 14 Nov 2019 15:40:33 -0500 In-Reply-To: <87eeya49hf.fsf@ambrevar.xyz> 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: Pierre Neidhardt Cc: Guix-devel On Thu, 14 Nov 2019 19:07:56 +0100 Pierre Neidhardt wrote: > See https://issues.guix.gnu.org/issue/38211. > Cool, thanks for building it! As for the issue, I don't know if the Jami version I use is stable, unfortunately some versions from the tarball repo contain bugs. I can ask the devs about it. I wanted to check if Jami compiles at all with the current state of work, not to break already working things. Now, because we know it compiles, I can improve the quality of the package and its dependencies, and of course keep it updated. My ideas: - what about handling the package in a modular way and instead of having three separated packages, can we have one package with many outputs? For example jami:libring, jami:client-gnome, jami:libringclient, etc. - finishing pjproject - the current package doesn't work at all, what works is pjproject-jami, because we disable some features. To prevent further breaking and not to keep a broken package it would be a right thing to do to finish it. - support for other operating systems (???) Guix probably doesn't support this now, but we could build every Jami client in a reproducible way. - easy to use Jami packages with guix pack for other distributions, using different init systems (support for autostart)? Or we can skip this and hope people will install Guix on their systems :) - Jami daemon (libring) service for the Shepherd? I could do this, but I would have to learn about the Shepherd and daemons, since I know almost nothing. - a small tutorial about maintaining a package, from the perspective of someone, who didn't know much about build systems and packaging. Things like where do you look for the needed dependencies, etc. Jan Wielkiewicz