<oriansj>janneke: so thoughts on the new mes-m2 primitive format? ***z3ntu is now known as z3ntu_
<janneke>oriansj: i am making some (much slower) progress with m2'ifying too and i was wondering; i think iwbn to split off building of mes-m2 from the x86/kaem.run of the mescc-tools-seed (or otherwise to have a variant that enables building all mescc-tools but not any mes, which is really the next stage)? <janneke>there is no hurry, i am working to make the mes srfi-9 record interface exactly as Guile <janneke>and am playing with/looking into a proper guile module setup, that mes currently fakes <oriansj>splitting of mes-m2 from mescc-tools-seed is fine by me <oriansj>I figured by incorporating it into a single step process; it'll make it easier for other distros to pickup our bootstrap starting point <oriansj>kaem --verbose --strict -> MesCC with a guile script that can run on mes-m2 to bootstrap GCC <oriansj>and don't be afraid of breaking the M2-Planet build, I can always get it working again when we have proper tests <oriansj>and as you are going to redo the module system; I'll strip out the current version and use it to clean up a few things <janneke>oriansj: yes, i found it very easy to use... <janneke>so maybe we could keep it; but as an option <janneke>kaem.run could maybe just invoke: kaem .. -f mescc-tools.kaem; kaem .. -f mes-m2.kaem; <janneke>oriansj: stripping it out sounds great, i make things more powerful; you strip the cruft out :-) <oriansj>janneke: agreed; I strip and you add ^_^ I guess I get the title the bootstripper :-p