Re: cleaning up the binaries in the coming Frescobaldi flatpak package

2020-10-22 Thread Jonas Hahnfeld
Am Mittwoch, den 21.10.2020, 23:44 +0200 schrieb Federico Bruni: > Il giorno mar 20 ott 2020 alle 22:59, Jonas Hahnfeld > ha scritto: > > No, I think you actually only need "gs" and you can disable a few more > > things from Ghostscript if only used by LilyPond. I've tried to build > > very minim

Re: cleaning up the binaries in the coming Frescobaldi flatpak package

2020-10-21 Thread Federico Bruni
Il giorno mar 20 ott 2020 alle 22:59, Jonas Hahnfeld ha scritto: The dependencies are also built by flatpak (so not the "official" binaries) and the process is steered through the yaml file that you submitted, right? (https://github.com/flathub/flathub/pull/1277) Yes! No, I think you actual

Re: cleaning up the binaries in the coming Frescobaldi flatpak package

2020-10-20 Thread Aaron Hill
On 2020-10-20 1:24 pm, Federico Bruni wrote: Some binaries are created while building lilypond dependencies. I'm concerned in particular with the bigger ones from ghostscript. Do I really need gpcl6 and gxps? Those would be for supporting XPS or PCL/PXL formats, if I understand it correctly.

Re: cleaning up the binaries in the coming Frescobaldi flatpak package

2020-10-20 Thread Jonas Hahnfeld
Am Dienstag, den 20.10.2020, 22:24 +0200 schrieb Federico Bruni: > I'm working on a Linux flatpak package for Frescobaldi which will > bundle LilyPond stable (currently 2.20). > > In order to reduce the size of the final flatpak, I want to remove the > binaries which are not needed to _run_ lily

cleaning up the binaries in the coming Frescobaldi flatpak package

2020-10-20 Thread Federico Bruni
I'm working on a Linux flatpak package for Frescobaldi which will bundle LilyPond stable (currently 2.20). In order to reduce the size of the final flatpak, I want to remove the binaries which are not needed to _run_ lilypond, lilypond-book or any other lilypond script. Some binaries are creat