IRC channel logs

2021-05-10.log

back to list of logs

<OriansJ>gforce_d11977: as a father, mothers day clearly is a day of a great deal of work. Extremely little of it is project related but by god is there a lot of work to do.
<melg8>does files directory handle subdirectories? when creating sysa from "packets"
<OriansJ>melg8: the syscall sys_mkdir is needed for making directories if I remember correctly
<melg8>maybe we are talking about different things, inside live-bootstrap - thee is a packets, for example like bison-3.4.1, which contains sometimes subfoler (files) - which is copied inside of folder in sysa. what i'm asking - if i will not just add files into this folders, but another folder with files like (lib + files inside) - would sysa copy hole
<melg8>thing correctly? or it adapted only to files
***ChanServ sets mode: +o rekado_
***rekado_ is now known as rekado
<bauen1>btw i'm seeing https://github.com/fosslinux/live-bootstrap/issues/112# happen very frequently (above 5% at least) happen in my runs
<bauen1>or at least 3 of the last 10 runs i'd guess
<stikonas>bauen1: well, #112 seems like a pregenerated file issue, maybe removing autotools files before ./bootstrap would help
<melg8>Hi, i'm now will start implementing logic about optional reproducibility flag, suggestions were to add file and inside it add a flag, source it inside of our run2.sh and use inside of system. So, any suggestions how to name this file with configuration variables? (currently suggested bootstrap.cfg). And in general any suggestions about
<melg8>implementation of that part?
<melg8>For context - original discussion (https://github.com/fosslinux/live-bootstrap/pull/115#discussion_r628554601)
<melg8>another question would be - should i add small options like FiX_TIMESTAMPS REMOVE_NON_REPRODUCIBLE_LOGS, FIX_FOLDER_NAMES etc. or just add single ENFORCE_DETERMINISM - which would trigger all actions needed to ensure that final image contains only deterministic results?
<bauen1>melg8: i like the more specific flags more
<bauen1>simply because things like e.g. REMOVE_NON_REPRODUCIBLE_LOGS can start to be moved into the "package" scripts
<bauen1>actually that was confusing
<bauen1>i meant having finer grained controls allows one to work on fixing one of them without the noise of everything else