Bug 557261

Summary:	perl-Padre: /blib contents should be properly installed, not deleted
Product:	[Fedora] Fedora	Reporter:	Chris Weyl <cweyl>
Component:	perl-Padre	Assignee:	Marcela Mašláňová <mmaslano>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	mmaslano, perl-devel
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	perl-Padre-0.50-2.fc13	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-02-05 09:45:24 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:
Bug Depends On:	557015
Bug Blocks:

Description Chris Weyl 2010-01-20 20:48:15 UTC

Recent changes in the main Perl package's handling of the module directory structure have resulted in shared files being installed incorrectly, e.. under /blib in the buildroot rather than where they should go.  See bug 557015 for more detail.

Padre leverages install_share() extensively, and the spec file simply removes them rather than installing them in the correct place.  This does not seem conducive to the proper functioning of Padre :)

I believe the proper resolution here would be to correct the issue in the main Perl package; this bug should remain open to track the issue in this package until it has been rebuilt with everything installed as upstream intended.

Comment 1 Marcela Mašláňová 2010-01-21 08:39:11 UTC

I thought there was mistake in Padre package, but now I'm aware of the problem in perl of Module::Build. Anyway all files are installed and application is functional. I've tested it. Files are "installed" twice into /blib and /usr/share. I'll do removal of 'rm -rf' as soon as building of packages is fixed.