aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2021-06-07 23:40:20 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2021-06-07 23:40:20 +0100
commitf88b104f6ed0f075e88d24163510cbb606e44b18 (patch)
tree54bf02c4444cb5e00e326dff538a68bf836b41f4 /reproduce/software
parente429b04514391bca517f777fab48a26c2303984b (diff)
Clarifications added to ReproZip in the appendix
After Boud posted a notice about Maneage in an online forum [1], Rémi Rampin and Vicky Rampin (from the ReproZip project) replied with some notes about our review of ReproZip in Appendix B. We are very grateful to both Rémi and Vicky for looking into it and for their comments, their contribution has been gratefully acknowledged with this commit. The relevant comments are listed below and have been addressed in this commit (see the 'diff' of this commit). - [Rémi Rampin] ReproZip can capture the build step if you want it to, it's just another command. So if you want to trace "make" and "pip install" etc before tracing your actual experiment, you will have all that build information. - [Rémi Rampin] Bundle size is easily fixed by not putting terabyte-sized data in the bundle, which is done by editing a simple configuration file. - [Vicky Rampin] Not all the files in the bundle are compiled/binary files [in relation to the old sentence "ReproZip just copies the binary/compiled files used in a project"]. [1] https://framapiaf.org/@boud/106296894758145705
Diffstat (limited to 'reproduce/software')
0 files changed, 0 insertions, 0 deletions