Bug 82083 – Fontconfig rpm replaces /etc/fonts/fonts.conf on install

Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours

Bug 82083 - Fontconfig rpm replaces /etc/fonts/fonts.conf on install

Summary:	Fontconfig rpm replaces /etc/fonts/fonts.conf on install

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	fontconfig (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Owen Taylor
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-01-17 04:12 EST by Nicolas Mailhot
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-17 09:40:59 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Nicolas Mailhot 2003-01-17 04:12:55 EST

Fontconfig rpm replaces /etc/fonts/fonts.conf on install. 

This is real annoying for people like me that customized /etc/fonts/fonts.conf
and have to put it back after every upgrade. Moreover this has no justification,
as far as I can tell the only thing that has been changing in this file for
quite a few rpm versions is the timestamp.

Please treat /etc/fonts/fonts.conf as a noreplace file

Comment 1 Owen Taylor 2003-01-17 09:40:59 EST

Read the top of the file... local configuration should go in local.conf.

(It only really make sense to make a file noreplace if it isn't expected
to change significantly. But fonts.conf encodes a lot of the details of
how we are setting up fonts.)

Comment 2 Nicolas Mailhot 2003-01-17 09:53:05 EST

Maybe one should put a big fat warning at the top of the file then.
Right now I really don't think anyone will notice the local.conf reference, it's
just lost in the mass.

Now I know it's here, I'll try to make good use of it

Comment 3 Nicolas Mailhot 2003-01-17 11:13:54 EST

In fact there *is* a warning.
But much too fat to be of any use.
I've just realized why I never saw the local conf ref : I just zap out when
people start writing about make install behaviour in rpm-provided files.

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