Re: Reproducible Research Hackathon: Friday, July 3rd
Paul Garlick writes: > One outstanding puzzle for me is to figure out how to test a package > definition in a new channel. For example, I have cloned the guix-past > repository and started to add a new package. However, what is the best > workflow to attempt a build from the channel? Do you add the channel > to the git checkout of guix? I did this from the checkout of “guix-past”: GUIX_PACKAGE_PATH=$PWD guix build my-package -- Ricardo
Re: [PATCH] doc: cookbook: Update entry about getting substitutes through Tor.
Hi Brice, dom 28 jun 2020 às 11:37:32 (1593355052), br...@waegenei.re enviou: > Hello André, > > I tought I already had applied your patch, but I forgot to do it. > It's now applied as f8945734a5abff69644284231cc47fb67456657b, sorry > for the delay. No big deal, thanks for your initiative. > I would love to know when you manage to advance on that front. It's currently beyond my understanding, but hopefully not for long. Cheers!
Re: [PATCH] Add Tor client only package definition
Hi Ludo, qui 02 jul 2020 às 11:36:24 (1593700584), l...@gnu.org enviou: > Hi André, > > Applied, but without those evil tabs that ‘guix lint’ reported. ;-) That's embarrassing. I could swear I had removed those before sending. > The closure as reported by ‘guix size’ is 96.7 MiB for ‘tor-client’ > vs. 97.0 MiB for ‘tor’. So it’s not compelling from that point of view, > but having less “dead” code when you only use the client is a probably > good idea. > > Thanks! I'm glad to have helped and hope to be able to contribute more. Tonight it's celebration time for me, I'll be drinking to the memory of those who came before and made it possible for me to be here now. :D > PS: In the future, please email guix-patc...@gnu.org to minimize chances > of losing sight of the patch: > https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html Sure thing. I've only sent it here because I was unsure if it was worth it. Thank you for all your work on guix!
Re: Reproducible Research Hackathon: Friday, July 3rd
Dear Pauk, On Fri, 03 Jul 2020 at 18:56, Paul Garlick wrote: > One outstanding puzzle for me is to figure out how to test a package > definition in a new channel. For example, I have cloned the guix-past > repository and started to add a new package. However, what is the best > workflow to attempt a build from the channel? Do you add the channel > to the git checkout of guix? I do not know if it is the best but I do: guix build -L path/to/clone the-package guix install -L path/to/clone the-package -p /tmp/test /tmp/test/bin/the-package Otherwise, I put in a channels.scm file something like: --8<---cut here---start->8--- (list (channel (name 'kikoo) (url "file:home/simon/path/to/clone") (branch "master")) (channel (name 'guix) ; avoid to recompute heavy derivations and build modules (url "https://git.savannah.gnu.org/git/guix.git";) (commit "000c7a0f70248ccf9dc774ef23da3e26d142c610")) --8<---cut here---end--->8--- where commit is something I already have in /gnu/store, then: guix pull -C channels.scm -p /tmp/loc /tmp/loc/bin/guix install foo -p /tmp/test but it is less convenient. All the best, simon
Re: Reproducible Research Hackathon: Friday, July 3rd
Hi Simon, Thank you for organising the day. > We are interested to hear your feedback. Especially about what pass, > what fail and what you have learnt, if you enjoyed the experience, or on > the contrary if you not, what could be improved for the next round. One outstanding puzzle for me is to figure out how to test a package definition in a new channel. For example, I have cloned the guix-past repository and started to add a new package. However, what is the best workflow to attempt a build from the channel? Do you add the channel to the git checkout of guix? Best regards, Paul.
Re: Reproducible Research Hackathon: Friday, July 3rd
zimoun writes: > On the Guix side, a missing feature is to search back in history, i.e., > somehow improves [2] (which starts 2019-01-01) and be able to find the > commit (or range of commits) which provided foo@x.y and bar@a.b > > 2: https://data.guix.gnu.org/repository/1/branch/master/package/boost I have been using things like “git log | grep -B10 "boost: Update"” to find the commit updating a package, and then “git show caffebabe…:gnu/packages/boost.scm” to view the file at the time of that commit. -- Ricardo
Re: Reproducible Research Hackathon: Friday, July 3rd
Dear, Thank you all for joining! A PAD is still open at: https://mensuel.framapad.org/p/guix-hackathon-9hlj?lang=en Please add whatever you have been up. Or drop an email. We are interested to hear your feedback. Especially about what pass, what fail and what you have learnt, if you enjoyed the experience, or on the contrary if you not, what could be improved for the next round. Personally, I spent the day with the good ol' Fortran and codes using the norm 77. And I have enjoyed the flexibility of Guix: navigate between the versions, running in container, etc.. For example, guix time-machine -C channels.scm -- build -L . foo guix time-machine -C channels.scm \ -- environment --container -L . foo --ad-hoc bar@x.y [env] ./configure --with-bar=xx && make And Guix helps a lot to expose "hidden" dependencies, i.e., not always explicitly mentioned in paper's instructions. Well, something that I learnt is you need some resource at hand, at least download or build the substitutes in advance. The "g77" issue [1] is not tackled but some points have been raised, so maybe soonish. :-) 1: https://github.com/ReScience/submissions/issues/41 On the Guix side, a missing feature is to search back in history, i.e., somehow improves [2] (which starts 2019-01-01) and be able to find the commit (or range of commits) which provided foo@x.y and bar@a.b 2: https://data.guix.gnu.org/repository/1/branch/master/package/boost Well, thank you all again! And hope to see you again on #guix-hpc. :-) Cheers, simon
