Bug 492605

Summary:	move the gargantuan collection of change logs from perl to perl-devel
Product:	[Fedora] Fedora	Reporter:	Stepan Kasal <kasal>
Component:	perl	Assignee:	Stepan Kasal <kasal>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	kasal, lkundrak, mmaslano, rc040203, robin.norwood, tcallawa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	5.10.0-68.fc10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-27 18:11:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stepan Kasal 2009-03-27 17:06:58 UTC

Generally speaking, detailed changelog files do not belong to %doc of the package.
%doc should prefer NEWS file, which should concisely describe user visible changes of the package.
It is possible to make an exception, if some of the following conditions are met:
- the changelog is short,
- the changelog is written in a user-geared style,
- the project fails to deliver a news file.

Speaking specifically about Perl:
It meets the last condition only, and I do not think it is sufficient for such an exception.
The change logs might be important to dig out when a particular feature was introduced or bug fixed.  But to satisfy this advanced user need, it is enough to pack the changelog collection in perl-devel.

Comment 1 Stepan Kasal 2009-03-27 18:11:12 UTC

Fixed in perl-5.10.0-65.fc11

Comment 2 Fedora Update System 2009-04-22 00:54:54 UTC

perl-5.10.0-68.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 3 Fedora Update System 2009-04-22 01:08:30 UTC

perl-5.10.0-68.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.