Re: source file ... .scm newer than compiled ... .go file

[Federico Bruni]

Il giorno dom 16 ott 2022 alle 21:35:39 +0200, Jean Abou Samra 
<jean@abou-samra.fr> ha scritto:
> Le 16/10/2022 à 20:41, Federico Bruni a écrit :
> > Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra 
> > <jean@abou-samra.fr> ha scritto:
> > > Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond 
> > > development a écrit :
> > > > > For the records, another application using Guile (GNU Cash) had 
> > > > > the
> > > > > same problem with flatpak three years ago.
> > > > > Their workaround was disabling recompilation. Bad idea or good 
> > > > > idea?
> > > > > https://github.com/flathub/org.gnucash.GnuCash/blob/master/patches/0001-Never-recompile.patch 
> > > > > 
> > > > Not really great. On the other hand, you only need a very targeted
> > > > installation and don't expect a fully functional Guile...
> > >
> > >
> > >
> > >
> > > Try really hard to avoid this. Some LilyPond libraries are written 
> > > in
> > > .scm files, like a lot of the stuff in openLilyLib. It is important
> > > to use compilation (by running with GUILE_AUTO_COMPILE=1) in order
> > > to get helpful error messages when something goes wrong there. If 
> > > this
> > > patch is used, as soon as one run with GUILE_AUTO_COMPILE=1 has been
> > > done, changes in the .scm files will have no effect, which is going
> > > to be very confusing for the user ...
> >
> > I'm afraid I have no alternative. The LilyPond 2.23.x version in 
> > flatpak doesn't currently work. I don't know when it started 
> > breaking, as I usually tested the stable only.
> > I opened a PR which makes 2.23.x work again:
> > https://github.com/flathub/org.frescobaldi.Frescobaldi/pull/14
>
>
>
> If all else fails, can you make it depend on the path so that files
> internal to Guile or LilyPond won't be recompiled but user files will?

I don't have the knowledge to work around this issue.
Currently I've patched Guile to disable automatic recompilation, so it 
won't work with any file, regardless of the path. If anybody can 
provide a patch which can disable automatic recompilation internal to 
Guile and LilyPond only, I'd be happy to apply it.

If I merge the flatpak PR tomorrow, can you test it with the edition 
engraver and report what happens?
If you don't have time, no problem and we'll wait for users to report 
it.

I don't have any spare time unfortunately and I can work on LilyPond 
only for small chunks of time during night.