[ungrafting] cURL is missing the 'curl-use-ssl-cert-env' patch

2020-12-12 Thread Marius Bakke
Hello, As you may have noticed, there is a new "ungrafting" branch that intends to remove most of the "grafts" people have to deal with on a regular basis. The CI (and undersigned) have gotten pretty far on building this branch, but there is a problem: cURL lost its "curl-use-ssl-cert-env" patch

Finding versions of packages (was: [outreachy] Walk through the Git history)

2020-12-12 Thread Ryan Prior
Hi there! I've been following the "guix git" discourse with interest because I know a lot of people who care about pinning packages to specific versions and selecting specific versions of software to install. This constituency currently relies heavily on systems like rvm, nvm, and conda to manage t

Re: [outreachy] Walk through the Git history (guix git {authenticate,log})

2020-12-12 Thread zimoun
Hi Mathieu, On Sat, 12 Dec 2020 at 09:42, Mathieu Othacehe wrote: >> 1. Loop with commit-parents as it is done for ’commit-closure’ in >> guix/git.scm. >> >> 2. Bind git_revwalk_* and use it instead. >> >> WDYT? >> >> Well, #1 is more straightforward but less efficient, IIUC. > > Running s

Re: [outreachy] Walk through the Git history (guix git {authenticate,log})

2020-12-12 Thread zimoun
Hi Magali, On Fri, 11 Dec 2020 at 16:01, Magali wrote: > I think #2 is the way to go. It may be more difficult to implement right > now, but in the future it'll make things easier if we think about adding > an option that allows us to choose the order the commits will be shown, > for instance.

...

2020-12-12 Thread Magali
Hey, On 12/12/2020 09:24, zimoun wrote: > Awaiting how to walk the history tree, I am proposing to use the loop as > Mathieu said. However, ’match’ is preferred over ’car’. I got curious as to why it is preferred, hehe. Is there a special reason? > Well, ’commit-list’ is far from perfect beca

[outreachy] Walk through the Git history

2020-12-12 Thread zimoun
Hey, On Sat, 12 Dec 2020 at 14:24, Magali wrote: >> Awaiting how to walk the history tree, I am proposing to use the loop as >> Mathieu said. However, ’match’ is preferred over ’car’. > > I got curious as to why it is preferred, hehe. Is there a special > reason? I do not really know. I am ju

Re: branch master updated: import/cran: Abort with error message when recursive import fails.

2020-12-12 Thread Ludovic Courtès
Hi, guix-comm...@gnu.org skribis: > commit 482b8ae2cd3f126a1300178e317df8993bf75b16 > Author: Ricardo Wurmus > AuthorDate: Sat Dec 12 00:06:18 2020 +0100 > > import/cran: Abort with error message when recursive import fails. > > Previously, after a failed recursive import "guix impo

Re: Guix day: Summary fo rust BoF session

2020-12-12 Thread Hartmut Goebel
Am 11.12.20 um 21:39 schrieb John Soo: I started with some talking points which I will attach. Many thanks -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |

Re: [outreachy] Walk through the Git history (guix git {authenticate,log})

2020-12-12 Thread Mathieu Othacehe
Hello zimoun, > 1. Loop with commit-parents as it is done for ’commit-closure’ in > guix/git.scm. > > 2. Bind git_revwalk_* and use it instead. > > WDYT? > > Well, #1 is more straightforward but less efficient, IIUC. Running something like: --8<---cut here---start