Bug 158779 - duplicate opens___.ttf file in main MSI archive and deb packages
Summary: duplicate opens___.ttf file in main MSI archive and deb packages
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
24.8.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks: Win-Installer-Smaller Installer-Linux
  Show dependency treegraph
 
Reported: 2023-12-19 13:39 UTC by Jérôme
Modified: 2024-01-02 19:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jérôme 2023-12-19 13:39:28 UTC
The daily build MSI archive contains the below duplicate file reported by fdupes :
Fonts/opens___.ttf
LibreOfficeDev 24:./program/resource/common/fonts/opens___.ttf

This file uses 203 kB.
Comment 1 Mike Kaganski 2023-12-19 16:12:09 UTC
Note that we instal OpenSymbol as a system font (inherited behavior; possibly still useful, if users depend on that font on their systems); and since tdf#128226 got fixed, we also install it as an internal resource (so if a user removes it from system, it's still available for LibreOffice, which uses it in e.g. Math, bullets, etc., so it is needed).
Comment 2 Jérôme 2023-12-19 17:38:28 UTC
This font is also duplicated in 2 deb packages.

In lodevbasis24.8-core_24.8.0.0.alpha0-1_amd64.deb :
/opt/libreofficedev24.8/program/resource/common/fonts/opens___.ttf

In lodevbasis24.8-ooofonts_24.8.0.0.alpha0-1_amd64.deb :
/opt/libreofficedev24.8/share/fonts/truetype/opens___.ttf
Comment 3 Jérôme 2023-12-23 16:09:32 UTC
Could we use a symbolic link file ?
Comment 4 Stéphane Guillou (stragu) 2024-01-02 15:53:37 UTC
Mike, was there any reason to keep the older system installation of the font, now that we have it internally? I see you said "[users might] depend on that font on their systems" but I don't see how the font being used in a different program is LO's responsibility.
Or is it something else, like internal fonts not being exposed in e.g. LO's font comboboxes?
Comment 5 Mike Kaganski 2024-01-02 16:05:49 UTC
(In reply to Stéphane Guillou (stragu) from comment #4)
> I don't see how the font being used in a different program is LO's responsibility.

Huh? This font is maintained in LibreOffice project (the only one such font). For decades, it was installed to users' boxes system-wide (since OOo times). And now you suggest that e.g. I take responsibility to say "hey, you used something created by us, installed by us, and now we decide that we make it unavailable for general use"? ;-) At least, it's not me, and it should come out of some discussion.
Comment 6 Stéphane Guillou (stragu) 2024-01-02 19:01:21 UTC
(In reply to Mike Kaganski from comment #5)
> (In reply to Stéphane Guillou (stragu) from comment #4)
> > I don't see how the font being used in a different program is LO's responsibility.
> 
> Huh? This font is maintained in LibreOffice project (the only one such
> font).
Well, that's the bit of information I was missing! :)
I had no idea we initiated and maintained OpenSymbol. Makes more sense that we wouldn't take the system installation away then.