Re: New branch guile-v3-work ?

[Thomas Morley]

Am Do., 23. Jan. 2020 um 10:48 Uhr schrieb Thomas Morley
<address@hidden>:
>
> Am Do., 23. Jan. 2020 um 10:35 Uhr schrieb David Kastrup <address@hidden>:
> >
> > Thomas Morley <address@hidden> writes:
> >
> > > Hi,
> > >
> > > I once pushed the /dev/guile-v2-work-branch to our repo.
> > > Would it be of help to have a /dev/guile-v3-work as well?
> > > If so, I'd need to do some clean up, currently my lily-guile3-build is
> > > a bit messy.
> >
> > Can you summarize the differences?  If there are extensive changes, we
> > probably want most of the solution in the main source code or
> > rebasing/cherry-picking becomes a nightmare.
> >
> > --
> > David Kastrup
>
> From my local branch, mostly on top of guile-v2-work (with comments):
>
> hermann@kasten ~/lilypond-git-guile-3.0 (dev/21-1-2020-test-guile3)$
> git log --oneline
>
>    probably in master soon:
> 16df8129ba (HEAD -> dev/21-1-2020-test-guile3) Han-Wens patch about
> ly_scm_write_string
>
>   gettext-changes for recently added/modified regtests:
> fe3fd55f95 Changes for recent regtests
>
> 47595f0f31 Let aclocal.m4 and configure.ac accept guile-config with version 3
>
> a8485e226d Guile-3 uses G_ for gettext instead of previous _
>
> 114b337d02 Let configure work with guile 3.0
>
> 26cbcda51a Work-around to fix utf-8-meta-data for >= guile-2.2.4
>
> 1ab8714f8b Initialize locale in lily.scm
>
>   Suggestion by Arne Babenhausen form the guile-list about
>   "ly:encode-string-for-pdf"
>   and

After Issue 5665 Remove broken and undocumented tracing features
https://sourceforge.net/p/testlilyissues/issues/5665/
this is superfluous:

>   adding (ice-9 threads)) to the used modules in memory-trace.scm
> 6a497e2b58 Suggestions by Arne
>
>   Simply commenting all previous functionality of ly:protects
> 1a688b3103 ly:protects doesn't work with guilev2
>
> Cheers,
>   Harm