From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adonay Felipe Nogueira Subject: Re: Continuing the work on the recipes related to GNU Ring Date: Fri, 31 Mar 2017 16:05:23 -0300 Message-ID: <87o9whferw.fsf@openmailbox.org> References: <87shma18an.fsf@openmailbox.org> <87a88d3yql.fsf@openmailbox.org> <871stmgs1y.fsf@openmailbox.org> <87shm2fcmr.fsf@openmailbox.org> <87inmwrx5t.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45557) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cu1rY-0001aV-Vf for guix-devel@gnu.org; Fri, 31 Mar 2017 15:05:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cu1rV-0004Yv-Rj for guix-devel@gnu.org; Fri, 31 Mar 2017 15:05:32 -0400 Received: from lb1.openmailbox.org ([5.79.108.160]:34984 helo=mail.openmailbox.org) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cu1rV-0004Xy-GU for guix-devel@gnu.org; Fri, 31 Mar 2017 15:05:29 -0400 In-Reply-To: <87inmwrx5t.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 26 Mar 2017 15:21:34 +0200") 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: guix-devel@gnu.org About sending patches for each package definition separatedly: Will do! :) However, I'd like to refrain from doing it now while the package's specific configure/make/build options in their "rules.mak" files aren't addressed clearly. This is an ongoing discussion at: [[http://lists.gnu.org/archive/html/ring/2017-03/msg00005.html]]. Some people contributed with useful information. However, the custom options for pjsip/pjproject are still somewhat unclear for me (except for the `--with-ssl=3Dgnutls` option, which is related to "gnutls" patch, and for which if they were to use OpenSSL, there would be a licensing issue, according to replies to a bug report referenced in the discussion). Of course, if Guix project wants to, I can make the set of recipes into separated patches anyways, with all customizations applied anyways, and still watch for that discussion. However, due to the amount of patches and since I don't have confirmation that the patches are being sent to Ring's upstreams, I would still have to decide between: a. Taking Ring's patches and registering them formerly at "gnu/packages/patches" directory (and related files), and then use apply-patch and similar procedures. This would allow better control of which patches are applied, but future version upgrades for the packages would need testing to see if the patches were applied. b. Leave the phases that deal with patches as they are. This would allow future patches to be picked up as long as the temporary "savoir-faire-linux-patches" package definitions are updated accordingly, but might also cause future upgrades to not have the patches applied (because the custom phases name the patches that are wanted). Personally, I'm more towards choosing (a). But I would like other's opinions. Respectfully, Adonay. --=20 - [[https://libreplanet.org/wiki/User:Adfeno]] - Palestrante e consultor sobre /software/ livre (n=C3=A3o confundir com gratis). - "WhatsApp"? Ele n=C3=A3o =C3=A9 livre, por isso n=C3=A3o uso. Iguais a el= e prefiro Ring, ou Tox. Quer outras formas de contato? Adicione o vCard que est=C3= =A1 no endere=C3=A7o acima aos teus contatos. - Pretende me enviar arquivos .doc, .ppt, .cdr, ou .mp3? OK, eu aceito, mas n=C3=A3o repasso. Entrego apenas em formatos favor=C3=A1veis ao /soft= ware/ livre. Favor entrar em contato em caso de d=C3=BAvida. - "People said I should accept the world. Bullshit! I don't accept the world." --- Richard Stallman