From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: New topic: packaging Date: Sun, 17 Feb 2019 10:02:26 +0100 Message-ID: References: <20190213101322.58e3f151@alma-ubu> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----UU809JTGS6O3BTXGDVHZ4CGK88IGTN" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:34245) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gvozZ-0005YS-IA for guix-devel@gnu.org; Mon, 18 Feb 2019 14:54:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gvozX-0002pN-Ma for guix-devel@gnu.org; Mon, 18 Feb 2019 14:54:17 -0500 Received: from mx1.riseup.net ([198.252.153.129]:41774) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gvozT-0002j9-QY for guix-devel@gnu.org; Mon, 18 Feb 2019 14:54:14 -0500 In-Reply-To: <20190213101322.58e3f151@alma-ubu> 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: =?ISO-8859-1?Q?Bj=F6rn_H=F6fling?= , Laura Lazzati Cc: Guix-devel ------UU809JTGS6O3BTXGDVHZ4CGK88IGTN Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable "Bj=C3=B6rn H=C3=B6fling" skrev: (1= 3 februari 2019 10:13:22 CET) >On Mon, 11 Feb 2019 11:38:21 -0300 >Laura Lazzati wrote: > >> Hi Guix again! >>=20 >> Another topic is about showing how to package=2E >>=20 >> G=C3=A1bor suggested maybe using my experience about creating a new R >> package=2E >>=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=2E WDTY? > >Aggreed on R: There is the importer to show, and R-packages are usually >easy to go=2E > >We have the rough idea of steps to take in the manual=2E Point people to >the right chapter here=2E > >Then it would involve the whole things: > >* git clone =2E=2E=2E >* go into guix directory >* Enter the environment: > guix environment guix > --> Explain what happens here and what's so cool about it=2E >* =2E/bootstrap >* =2E/configure --localstatedir=3D/var >* make >* Then the import begins: >* =2E/pre-inst-env guix import =2E=2E=2E >* [hack file, using emacs, maybe =2E/pre-inst guix edit new-package] >* =2E/pre-iinst-env guix build new-package >* Check: > =2E/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=2E > >Bj=C3=B6rn Hi=2E Am I late to the party? Here is my two cents=2E I suggest splitting this in multiple videos=2E Split after make is finished=2E I agree it is hard to cover less than this if we want to nudge people into= contributing new packages and guide them the whole way=2E If you decide to go with=20 =2E/pre-inst guix edit new-package=20 then I suggest we fool proof it by prepending EDITOR=3Demacs Given this I suggest the video starting after make also include setting up= emacs=2E This might even warrant its own short video=2E So we end up with = 3! Generally I think shorter videos to the point are preferred over long ones= bundling multiple things=2E Maybe we should cut it also after successful build and test and make the c= omitting a separate video=2E That gives us 4 in total =F0=9F=98=83 --=20 Sent from my k-9 mail for Android=2E ------UU809JTGS6O3BTXGDVHZ4CGK88IGTN Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
"Bj=C3=B6rn H=C3=B6flin= g" <bjoern=2Ehoefling@bjoernhoefling=2Ede> skrev: (13 februari 2019 1= 0:13:22 CET)
On Mon, 11 Feb 2019 11:38:21 -0300
Laura Lazzati =
<laura=2Elazzati=2E15@gmail=2Ecom> wrote:

Hi Guix again!

Another topic is about s=
howing how to package=2E

G=C3=A1bor suggested maybe using my experie=
nce about creating a new R
package=2E

My idea is to show how to l=
ook 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=2E WDTY?

Aggreed on R: There is the importer to show, and R-packages are=
 usually
easy to go=2E

We have the rough idea of steps to take in=
 the manual=2E Point people to
the right chapter here=2E

Then it =
would involve the whole things:

* git clone =2E=2E=2E
* go into g=
uix directory
* Enter the environment:
  guix environment guix
  -=
-> Explain what happens here and what's so cool about it=2E
* =2E/boo=
tstrap
* =2E/configure --localstatedir=3D/var
* make
* Then the im=
port begins:
* =2E/pre-inst-env guix import =2E=2E=2E
* [hack file, u=
sing emacs, maybe =2E/pre-inst guix edit new-package]
* =2E/pre-iinst-en=
v guix build new-package
* Check:
  =2E/pre-inst-env guix lint new-pa=
ckage
* Finally:
  Commit, take care of the correct commit messsages<=
br>* git format-patch and maybe git send-email

This is a lot for eve=
n a simple R package but I don't see how/where we
could leave out steps =
without confusing people=2E

Bj=C3=B6rn


Hi=2E

Am I late to the party?

Here is my= two cents=2E

I suggest splitting this in multiple videos=2E
Spli= t after make is finished=2E

I agree it is hard to cover less than th= is if we want to nudge people into contributing new packages and guide them= the whole way=2E

If you decide to go with
=2E/pre-inst guix edi= t new-package
then I suggest we fool proof it by prepending EDITOR=3Dem= acs

Given this I suggest the video starting after make also include = setting up emacs=2E This might even warrant its own short video=2E So we en= d up with 3!

Generally I think shorter videos to the point are prefe= rred over long ones bundling multiple things=2E

Maybe we should cut = it also after successful build and test and make the comitting a separate v= ideo=2E That gives us 4 in total =F0=9F=98=83
--
Sent from my k-9 ma= il for Android=2E
------UU809JTGS6O3BTXGDVHZ4CGK88IGTN--