Bug 5051

Summary:	app-defaults files install to libdir instead of datadir
Product:	xorg	Reporter:	Mike A. Harris <mharris>
Component:	* Other	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	high	CC:	gajownik
Version:	6.99.99.902 (7.0 RC2)
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	1690

Description Mike A. Harris 2005-11-15 07:11:18 UTC

The X11/app-defaults files are architecture-independent data, which should
be installed in /usr/share on FHS compliant systems.  This would be
/usr/share/X11/app-defaults on FHS compliant Linux distributions.

I found a CVS commit from recent:

Log message:
  Change default install dir for app-default files from
  $(sysconfdir)/X11/app-defaults to $(libdir)/X11/app-defaults to match
  the monolith & allow localization


This probably should be changed to $(datadir), and then ./configure should
set datadir to the relevant place for the given OS/platform.  That would
be /usr/share on Linux.

This affects all Xorg packages that install app-defaults.  Similar problem
occurs for all of the fonts packages.  Fonts are arch-independent data which
should be installed into /usr/share on FHS compliant Linux systems.

rgb.txt is another one.

Comment 1 Alan Coopersmith 2005-11-16 12:53:22 UTC

Xorg default paths are not intended to be FHS compliant.   If you want to add
options to optionally enable FHS compliance, please submit patches, but the
default should be to maintain compatibility with traditional install locations,
and not break platforms for which FHS is not desired.

Comment 2 Adam Jackson 2005-11-30 17:04:54 UTC

we decided today that app-defaults are data (and therefore located by datadir),
that Xt should export the app-default directory from its .pc file, and that Xt
should be extended to scan /usr/share/blah as well by default.

Comment 3 Kevin E. Martin 2005-12-09 17:29:17 UTC

Fixed in CVS.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.