From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: [outreachy] Further steps Date: Thu, 25 Oct 2018 16:37:27 +0200 Message-ID: References: <20181024071635.29543fcf@alma-ubu> <877ei67mfq.fsf@elephly.net> 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]:54064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFgla-0005bF-Tu for guix-devel@gnu.org; Thu, 25 Oct 2018 10:37:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFglZ-0002a9-IF for guix-devel@gnu.org; Thu, 25 Oct 2018 10:37:42 -0400 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 , Ricardo Wurmus Hello Laura, Laura Lazzati ezt =C3=ADrta (id=C5=91pont: 201= 8. okt. 25., Cs, 16:17): > > On Thu, Oct 25, 2018 at 12:08 AM Ricardo Wurmus wrot= e: > > > > > > Hi Laura, > > > > >> > If you have any other favourite packages, you can give them also a= try. > > >> > It could just get more difficult, with more manual steps, other bu= ild > > >> > systems, dependencies to be packed first, code to be patched, etc. > > >> > > > >> > > >> Yes, this would also be good. Please tell us if you have any specifi= c package > > >> in mind. > > > I guess I could package some more R packages, and then let me know > > > which ones you think are more convenient, or you find more appealing > > > for Guix. > > > > All free R packages on CRAN are appealing from my perspective. You can > > also pick a package from Bioconductor, which might be a tad more > > difficult, as that could depend not only on other Bioconductor packages > > but also packages on CRAN. Note that the importer does not > > automatically switch between downloading from Bioconductor to > > downloading from CRAN, so you may have to run the importer more than > > once. > > > > Use =E2=80=9Cguix import cran -a bioconductor -r PACKAGE=E2=80=9D =E2= =80=94 when it aborts you > > may have stumbled upon an unpackaged CRAN package. > > > > R packages from Bioconductor should be added to the (gnu packages > > bioconductor) module. > > > Yes, I was thinking that maybe a trade-off between learning new things > and contributing with things that you need right now, that was why I > was thinking of R packages. Maybe I could package one or two more, to > practice doing so by myself this time, and then switch to another > task, WDYT? That would be great! > BTW, I was trying to run guix pull, the one installed on top of my > foreing distro - not the one in the guix environment - and I am > getting this error, don't know why, I have already run guix pull > before: > :~/guix$ guix pull > Migrating profile generations to '/var/guix/profiles/per-user/laura'... > guix pull: error: symlink: File exists: > "/var/guix/profiles/per-user/laura/current-guix-1-link" It seems that something is mixed up between the old and new guix pull, I hope someone can provide some more insight. Ludo? > > As far as learning new things goes: R packages usually are very simple > > They rarely ever require changes to the build system, so you don=E2=80= =99t get > > to learn about the =E2=80=9Carguments=E2=80=9D field of the =E2=80=9Cpa= ckage=E2=80=9D DSL. > > > > Alternatively, you could look into making changes to the Texinfo > > documentation. For the project you would need to be somewhat familiar > > with the manual, so it can=E2=80=99t hurt if you would edit it a little= . An > > easy edit is to add a handful of =E2=80=9C@cindex=E2=80=9D lines to pla= ces in the manual > > that currently miss them. A =E2=80=9C@cindex=E2=80=9D line adds a loca= tion in the > > manual to the index for a given keyword, so that people can find > > relevant places in the manual more easily. > By the manual you, mean, > https://www.gnu.org/software/guix/manual/en/html_node/index.html#Top, > or am I missing something? There is the manual in the source tree, at doc/guix.texi. The one on the website is generated from that. > If that's the manual, please, let me know further steps to edit it, > since I don't have much idea of how to do so. You can modify the manual at doc/guix.texi, and send a patch the same way you would do for adding a package. Please note, that info is sometimes quite fussy about format, so try to rebuild the manual after modifications. > It also mentions that you need help for translations, my mother tongue > is spanish, and I am good at translating documentation, at least in > neutral latin american spanish, but I don't know if that is for > another project - I followed the link: Translation Project. > You are welcome to help with translations if you can find the time for that= . Translation Project is a hub, where different projects can send there po fi= les for translation. Usually there are language communities for a given languag= e, and they are coordinating translation work. This is orthogonal to this Outr= eachy project. However, it would be nice if you could provide the translations of the vide= os, once we get there, > Regards! > Laura > > > > > -- > > Ricardo > > Best regards, g_bor