FS#9939 - [foomatic-db-engine] perl file locations

Attached to Project: Arch Linux
Opened by Allan McRae (Allan) - Tuesday, 25 March 2008, 03:28 GMT
Last edited by Kevin Piche (kpiche) - Thursday, 24 April 2008, 01:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
foomatic-db-engine (3.0_20080211-1) puts perl files in /usr/lib/perl5/current/Foomatic which AFAIK is not inline with the perl policy.
This task depends upon

Closed by  Kevin Piche (kpiche)
Thursday, 24 April 2008, 01:48 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Problem not related to perl module file locations.
Comment by Kevin Piche (kpiche) - Wednesday, 26 March 2008, 02:54 GMT
I've already modified the foomatic-db-engine PKGBUILD for when the maintainer releases the next version.
Comment by Maciej Libuda (Mefju) - Wednesday, 26 March 2008, 11:10 GMT
After upgrade to latest perl, my printer is not working anymore. I think it's related with this bug.
Comment by Kevin Piche (kpiche) - Thursday, 27 March 2008, 00:31 GMT
The file locations may not conform to the new perl policy but the package should still work since the old /usr/lib/perl5/current directory is included in @INC.

$ pacman -Q perl
perl 5.10.0-3
$ perl -e 'use Foomatic::Defaults;
use Foomatic::DB;
use Foomatic::PPD;
use Foomatic::UIElem;'
$

And since there are no *.so libraries no recompilation is required. Unless you have an error message or log output showing a problem I can't see the module locations being a problem.
Comment by Maciej Libuda (Mefju) - Tuesday, 01 April 2008, 08:07 GMT
You're right. Problem with my printer is because of that bug  FS#9935 .

Loading...