I expect this has been considered before, but what is it that makes it unpalatable to have a step like initex for TeX to build the .go files upon installation?
Wouldn't it solve the issue at hand? (The portability would be addressed by the fact that it's the target platform to build online, and you'd have a certain tolerance for variability at the destination site that you could mop up with a process like that would be difficult to handle apriori, I guess short of producing several built packages) L On Tue, Feb 22, 2022 at 6:29 PM Karlin High <karlinh...@gmail.com> wrote: > On 2/22/2022 10:55 AM, Werner LEMBERG wrote: > > In particular, we can't tell non-developers "Please use the > > current development version, which works very reliably" and introduce > > a severe slowness at the same time. > > Perhaps that advice could be suspended for one series of development > versions? Doing one last Guile 1.8 stable release before the Guile 2.2 > transition, then advising to stick with that if interim slowness in > development versions is unacceptable. > -- > Karlin High > Missouri, USA > >
