lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilyglyphs not found in ubuntu packages 20.04


From: Urs Liska
Subject: Re: lilyglyphs not found in ubuntu packages 20.04
Date: Fri, 28 Aug 2020 22:06:36 +0200
User-agent: Evolution 3.36.4-2

Hi Bart,

thanks for reminding.

Am Freitag, den 28.08.2020, 21:20 +0200 schrieb bart deruyter:
Hi all,

I would need to start working on my project again, using luatex, lilypond, lyluatex and lilyglyphs. But lilyglyphs appears to be missing from the ubuntu packages. This summer I upgraded to 20.04 though, and I found out to my surprise, lilyglyphs is missing. It is present in 'eoan' though.

I already contacted the developer but only heard from him it is missing indeed and he did not know why either.
Maybe someone here knows what has been going on.

I asked on the texlive mailing list, and I got an answer, but I didn't manage following through

Am Freitag, den 03.07.2020, 07:41 +0900 schrieb Norbert Preining:
> Hi Urs,



> > Someone posted an issue that lilyglyphs.sty seems to be missing in
> > TeX
> > Live after updating to Ubuntu 20.04.


> And in Debian. Because it depends on Python2 the last time I checked,

> and Python2 programs are not acceptable anymore in Debian and Ubuntu:



> From my Debian package building config file (ignore the syntax
> around)

>         # python3 purge - blacklist all packages that don't have py3
> support

>         blacklist;tpm;ebong;*

>         blacklist;tpm;de-macro;*

>         blacklist;tpm;lilyglyphs;*

>         blacklist;tpm;pygmentex;*

>         blacklist;tpm;sympytexpackage;*



> Update to Python3 version of the scripts is necessary.

So the workaround would be to either update the helper scripts to Python 3 or to drop these scripts. Off the top of my head I don't know how important these scripts actually are or how complex it would be to update them.

They are used to create sets of new notation elements. IIRC.
My personal gut feeling would be to drop support for lilyglyphs altogether because lyluatex can do everything lilyglyphs can, and better - i.e. without the need for pre-compiled PDFs. But - and that's a big but - the advantage of lilyglyphs is that it doesn't need to run LilyPond. *I* will always have LilyPond around, but for a general audience this would be a major limitation, I think.

Opinions?

Urs


reply via email to

[Prev in Thread] Current Thread [Next in Thread]