From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laura Lazzati Subject: Re: [outreachy] Further steps Date: Thu, 25 Oct 2018 11:55:21 -0300 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]:59515) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFh4Y-0002yu-0T for guix-devel@gnu.org; Thu, 25 Oct 2018 10:57:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFh3H-0006Qi-Jw for guix-devel@gnu.org; Thu, 25 Oct 2018 10:56:00 -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: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Cc: Guix-devel , Ricardo Wurmus On Thu, Oct 25, 2018 at 11:37 AM G=C3=A1bor Boskovits = wrote: > > Hello Laura, > > Laura Lazzati ezt =C3=ADrta (id=C5=91pont: 2= 018. > okt. 25., Cs, 16:17): > > > > On Thu, Oct 25, 2018 at 12:08 AM Ricardo Wurmus wr= ote: > > > > > > > > > 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 = build > > > >> > systems, dependencies to be packed first, code to be patched, et= c. > > > >> > > > > >> > > > >> Yes, this would also be good. Please tell us if you have any speci= fic 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 appealin= g > > > > for Guix. > > > > > > All free R packages on CRAN are appealing from my perspective. You c= an > > > also pick a package from Bioconductor, which might be a tad more > > > difficult, as that could depend not only on other Bioconductor packag= es > > > 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! Ok then, I start with a new R package, and then send the patch. > > > 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? Yes please, I need to fix this before going on. Here is what happened, so that I provide the full information After having my patch approved, I ran git pull (on master branch, of course, I then created branches) I wanted to check that everything was fine, so I ran: :~/guix$ guix package -s "^r" | recsel -p name description| grep '\S' | sort >newR.txt And got the output: Command 'recsel' not found, but can be installed with: sudo apt install recutils (which is strange, I have played with recsel before sending my patches, when learning guix package command) so i ran guix package -I, where recutils was effectively installed However, I tried: $guix package -i recutils guix package: warning: Your Guix installation is 13 days old. guix package: warning: Consider running 'guix pull' followed by 'guix package -u' to get up-to-date packages and security updates. The package was installed after those warnings, and I was asked to export env variables: export PATH=3D"/home/laura/.guix-profile/bin${PATH:+:}$PATH" export INFOPATH=3D"/home/laura/.guix-profile/share/info${INFOPATH:+:}$INFOP= ATH" Did so, but when running again: :~/guix$ guix package -s "^r" | recsel -p name description| grep '\S' | sort >newR.txt Got the output: recsel: error: cannot read file description And also got that error when running guix pull. > > > > As far as learning new things goes: R packages usually are very simpl= e > > > 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=9C= package=E2=80=9D DSL. > > > > > > Alternatively, you could look into making changes to the Texinfo > > > documentation. For the project you would need to be somewhat familia= r > > > with the manual, so it can=E2=80=99t hurt if you would edit it a litt= le. An > > > easy edit is to add a handful of =E2=80=9C@cindex=E2=80=9D lines to p= laces in the manual > > > that currently miss them. A =E2=80=9C@cindex=E2=80=9D line adds a lo= cation 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 th= at. > Translation Project is a hub, where different projects can send there po = files > for translation. Usually there are language communities for a given langu= age, > and they are coordinating translation work. This is orthogonal to this Ou= treachy > project. > > However, it would be nice if you could provide the translations of the vi= deos, > once we get there, > > > Regards! > > Laura > > > > > > > > -- > > > Ricardo > > > > > Best regards, > g_bor