<stikonas[m]>bauen1: I guess best option would be to resolve them <stikonas[m]>Avoid using unversioned binaries in some packages, e.g. automake <bauen1>yes, that's what was my first idea too, just don't install unversioned automake, since that is probably asking for trouble anyways <stikonas[m]>Well, but for package upgrades we need to be able to uninstall stuff <stikonas[m]>Probably trivial with xbps but not yet implemented for our binary .tar.bz2 packages <stikonas[m]>And there is some pre-package stuff from early kaem scripts but hopefully not too much <oriansj>theruran: if you look at stage3/inital_library.fs (in stage0) <oriansj>you will see all that is required to run the stage0 FORTH and how to extend it immediately in FORTH <oriansj>I understand the appeal of interpreted languages as a user of said languages, however I know the pain of actually debugging them while trying to create them and try to avoid the experience as much as possible these days. <bauen1>actually i think `sysa/autoconf-2.53/stage1.sh` is using automake-1.6 when it should be using automake-1.4-p6 which was only masked because tar didn't really handle the hardlinks properly leading it to use automake-1.4-p6 anyway <bauen1>or at least it still fails when not doing unlink-first and removing the hardlinks, leading to correct automake-1.4 and automake-1.6 binaries <bauen1>same problem with /usr/bin/aclocal ***genr8eofl__ is now known as genr8eofl
***genr8eofl_ is now known as genr8eofl
<janneke>hmm m2-planet 1.8.0 identifies as 1.7.0 ***genr8eofl_ is now known as genr8eofl
<bauen1>i feel like complaining about long compile times is a bit ironic, given how nice it is that live-bootstrap is compiling so much (useful) things already ...