Re: Preservation of Guix (PoG) report 2023-03-13

Hello! Timothy Sample skribis: [...] >>> • Subversion support (for TeX-based documentation stuff, I guess) >> >> For the interested reader, details for helping in the implementation: >> >> https://issues.guix.gnu.org/issue/43442#9 >> https://issues.guix.gnu.org/issue/43442#11 > > Fa

Re: Preservation of Guix (PoG) report 2023-03-13

Hi Ludo, Ludovic Courtès writes: > Do you think this could be turned into a Guix System service, with an > eye towards making it run on project infrastructure? I need to revisit what you did with Disarchive and Cuirass. The process for the PoG report is very similar. I can’t jump into it righ

Re: Preservation of Guix (PoG) report 2023-03-13

Hey, Simon Tournier writes: > Well, I do not remember if you consider also the ’origin’ > (fixed-outputs) as ’inputs’ or ’patches’. Do you? I’m quite confident I’m getting everything. I’ll describe my approach, because I’m happy with it. :) The Guix package graph exists twice, essentially.

Re: Preservation of Guix (PoG) report 2023-03-13

Hi Timothy, Timothy Sample skribis: > Allow me to present to you a long-overdue update to the Preservation of > Guix (PoG) report: . 🎉 Yay, thank you!! Do you think this could be turned into a Guix System service, with an eye towards making it run on

Re: Preservation of Guix (PoG) report 2023-03-13

Hi, On Mon, 13 Mar 2023 at 19:37, Timothy Sample wrote: > Note that you can link to the most recent version of the report using > . Awesome! \o/ Well, I do not remember if you consider also the ’origin’ (fixed-outputs) as ’inputs’ or ’patches’. Do you?