Bug 2145088 - Drop dependency on xorg-x11-font-utils
Summary: Drop dependency on xorg-x11-font-utils
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-23 05:10 UTC by Peter Hutterer
Modified: 2022-11-23 06:29 UTC (History)
11 users (show)

Fixed In Version: xorg-x11-server-1.20.14-10.fc38
Clone Of:
Environment:
Last Closed: 2022-11-23 06:29:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
0001-configure.ac-search-for-the-fontrootdir-ourselves.patch (2.93 KB, patch)
2022-11-23 05:10 UTC, Peter Hutterer
no flags Details | Diff

Description Peter Hutterer 2022-11-23 05:10:02 UTC
Created attachment 1926558 [details]
0001-configure.ac-search-for-the-fontrootdir-ourselves.patch

The xserver build currently requires xorg-x11-font-utils. But the only reason it does is by calling some m4 macros that are provided by that package. And those again just resolve to: adding a --with-fontrootdir to configure and defaulting (eventually) to /usr/share/fonts/X11.

The macros also allow per-font subdirectory configuration but no-one needs this (e.g. this is not available in upstream's meson.build files where those subdirectories are hardcoded).

A better approach here would be to simply handle that configure flag ourselves, hardcoding the subdirectories and dropping the need for xorg-x11-font-utils.

There's little impact for Fedora. One package during the build is arguably meh and xorg-x11-font-utils cannot be removed until the legacy fonts are dropped. It has more advantages on RHEL though where we can drop that package.

This affects e.g. tigervnc since that will no longer require that package either.

Comment 1 Peter Hutterer 2022-11-23 06:29:56 UTC
Fixed in xorg-x11-server-1.20.14-10.fc38


Note You need to log in before you can comment on or make changes to this bug.