<zimoun>civodul: Giving a look at 2 things: merging 2 graphs and improving the generation of “pack -f docker” (based on nixery tricks), I note that the almost identical code appears in (guix graph), (guix build store-copy) and (guix import utils). Is it on purpose? Does it make to move the code (guix graph) and tweak the rest?
<rekado>zimoun: yes, it was me. A colleague of mine found it.
<rekado>this approach has one virtue: it is based on information that an unprepared person has.
<rekado>they might know that things worked three months ago, so they can install the version from three months ago without having to know anything more.
<rekado>I think the guix time-machine could benefit from something like that
<rekado>i.e. don’t give it a commit or a channels file but a relative time and have it figure out the rest
<rekado>makes time travel all that more timey whimey.
<zimoun>yes, it should not be too hard to implement. Well, even I will ask to Magali to add a first draft to “guix git log --date=YYYY-MM-DD” and return a range of commits. Then in another step, “guix time-machine” could accept a date. Somehow, it could be useful to fallback to MRAN.
<zimoun>However, dates is a fake impression that it is enough for reproducibility.