Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3508 - perl DB_File not found when building perl Cache
|
DetailsI've been trying to build the perl Cache module - http://search.cpan.org/~cleishman/Cache-2.03/lib/Cache.pm. One of the repequisites is DB_File => 1.72. I have the Arch package perl-5.8.7-1 installed, which includes DB_File 1.811. However, when I run perl Makefile.PL to start building Cache, a warning is displayed saying DB_File => 1.72 is missing.
I have two workarounds: 1) Create a local DB_File package for the current version 1.814, and force-install it over perl. 2) Create a local perl package, amending the PKGBUILD from [current] to use DB_File 1.814 instead 1.811. Either of these facilitates a successful build of Cache. |
This task depends upon
Closed by Judd Vinet (judd)
Friday, 30 December 2005, 20:41 GMT
Reason for closing: Fixed
Additional comments about closing: Updated DB_File to 1.814
Friday, 30 December 2005, 20:41 GMT
Reason for closing: Fixed
Additional comments about closing: Updated DB_File to 1.814
#cd ext
#rm -rf DB_File
#mv $startdir/src/DB_File-1.811 ./DB_File
so I now have perl with the originally-included version of DB_File - which oddly enough, seems to be 1.811, according to src/perl-5.8.7/ext/DB_File/Changes. I can build Cache against this version, but I don't know what conclusion can be drawn from that. And of course, there's the question of support for sleepycat's db 4.1.x.
Locally, I'm going with option 2 from my original post for the moment, but I'd like to put this stuff in the AUR, so I was hoping for a more "official" solution.