Bug 25096 – gs_init.ps and pdf_sec.ps should be marked %config

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 25096 - gs_init.ps and pdf_sec.ps should be marked %config

Summary:	gs_init.ps and pdf_sec.ps should be marked %config

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	ghostscript (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Crutcher Dunnavant
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-01-27 17:29 EST by Göran Uddeborg
Modified:	2007-04-18 12:30 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-04-18 19:28:32 EDT
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 Göran Uddeborg 2001-01-27 17:29:51 EST

If you live outside the US and use A4 paper, you are supposed to modify
gs_init.ps to make this default for ghostscript.

The file pdf_sec.ps is only a dummy, and contains instructions where to
find a real implementation.  It is intended to be replaced with the real
implementation.

It seems to me it would make sense to mark these two files as %config.

(In the case of pdf_sec.ps maybe it is no longer necessary to just ship a
dummy, now that the US export regulations have been changed.  In that case
an alternative method for that file would be to include the real
implementation in the package from the start.)

Comment 1 Crutcher Dunnavant 2001-04-18 19:28:28 EDT

 I agree, will investigate

Comment 2 Crutcher Dunnavant 2001-08-02 18:24:39 EDT

fixed.

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