From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QmrDtnJuIEjDtmZsaW5n?= Subject: Re: New topic: packaging Date: Wed, 13 Feb 2019 10:13:22 +0100 Message-ID: <20190213101322.58e3f151@alma-ubu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/MM6l=Gu7BM_S3i.iCZcwtc6"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:57712) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtqbo-0004Gn-JI for guix-devel@gnu.org; Wed, 13 Feb 2019 04:13:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtqbn-0005tE-Et for guix-devel@gnu.org; Wed, 13 Feb 2019 04:13:36 -0500 Received: from m4s11.vlinux.de ([83.151.27.109]:60426 helo=bjoernhoefling.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtqbl-0005ly-EE for guix-devel@gnu.org; Wed, 13 Feb 2019 04:13:35 -0500 In-Reply-To: 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: Laura Lazzati Cc: Guix-devel --Sig_/MM6l=Gu7BM_S3i.iCZcwtc6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 11 Feb 2019 11:38:21 -0300 Laura Lazzati wrote: > Hi Guix again! >=20 > Another topic is about showing how to package. >=20 > G=C3=A1bor suggested maybe using my experience about creating a new R > package. >=20 > My idea is to show how to look for a package that is not packaged, > package it and the workflow for testing it with git am and send it to > the patches list. WDTY? Aggreed on R: There is the importer to show, and R-packages are usually easy to go. We have the rough idea of steps to take in the manual. Point people to the right chapter here. Then it would involve the whole things: * git clone ... * go into guix directory * Enter the environment: guix environment guix --> Explain what happens here and what's so cool about it. * ./bootstrap * ./configure --localstatedir=3D/var * make * Then the import begins: * ./pre-inst-env guix import ... * [hack file, using emacs, maybe ./pre-inst guix edit new-package] * ./pre-iinst-env guix build new-package * Check: ./pre-inst-env guix lint new-package * Finally: Commit, take care of the correct commit messsages * git format-patch and maybe git send-email This is a lot for even a simple R package but I don't see how/where we could leave out steps without confusing people. Bj=C3=B6rn --Sig_/MM6l=Gu7BM_S3i.iCZcwtc6 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQiGUP0np8nb5SZM4K/KGy2WT5f/QUCXGPfsgAKCRC/KGy2WT5f /czjAKCuEAlNnyOk1Elkrxw2gP8idymeiQCcDy0zHJ+oo9iFaycufWiEpl2QiHA= =Hmqe -----END PGP SIGNATURE----- --Sig_/MM6l=Gu7BM_S3i.iCZcwtc6--