IRC channel logs

2021-05-24.log

back to list of logs

<oriansj>Melg817: well we already have some perl bootstrapped but progress is always welcomed across all paths.
<oriansj>we also have a mini-haskell bootstrapped too (bylnn-compiler); which with more work will solve the GHC haskell bootstrap problem.
<oriansj>fortunately we have mihi, who single handedly solved the Guile bootstrap problem with https://github.com/schierlm/guile-psyntax-bootstrapping
<oriansj>as the ratio of support:developers seems to be 5:1; assuming we maintain our histrocial growth rate, in 5 years we will finally be ahead of the curve and might be able to maintain an ever expanding and improving bootstrap forever.
<oriansj>^histrocial^historical^
<stikonas>well, we still need to build guile on live-bootstrap...
<stikonas>but we are probably not too far now
<oriansj>and once guile is properly bootstrapped, we can share and leverage the guix work.
<oriansj>making all future new languages a solved(ish) problem provided we start addressing them once they are available.
<vagrantc>hopefully we can make bootstrapping a thing that new languages consider from the get-go
<oriansj>vagrantc: long term hopefully but in the short term we limit the damage and slowly roll it back as we sort out each language's bootstrap.
<oriansj>Guix really helps with that long term, as functional package definitions will slowly absorb the packaging problem away from us.
<fossy>stikonas: yeah. I am not 100% sure
<fossy>Chroot might be best short term option
<Melg817>if env variable is set from child process - will other child processes which are executed later by kaem also get this updated env? or they will be using original env, which were from start of script.kaem run?
<oriansj>Melg817: that is trivial to test and prove. just write export foo=3 in file a and echo ${foo} in file b and have file 1 call a then b
<Melg817>i've tested, i think answer is no
<stikonas>hmm, somehow new coreutils is not aware of its own version
<stikonas>probably artifact of using git archive
<stikonas>/after # ls --version
<stikonas>ls (GNU coreutils) UNKNOW
<stikonas>not a critical issue, but might be nice to fix it
<stikonas>fossy: one minor point about double space but I gave you green tick
<fossy>Melg817: no, they will not
<fossy>i don't think that even bash does that
<fossy>yeah bash dosen't do that. kaem also doesn't
<pabs3>can someone update the website to not say freenode? https://bootstrappable.org/who.html
<siraben>hello all
<siraben>yay we have logs as well
<siraben>was just parting from my last freenode channels
<stikonas>siraben: logs are probably somewhere on that server, just not coppied...
***Server sets mode: +cnt