* Starting pop-before-smtp ... Can't locate DB_File.pm in @INC (@INC contains: /etc/perl /usr/lib/perl5/vendor_perl/5.8.8/i686-linux /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.7/i686-linux /usr/lib/perl5/vendor_perl /usr/lib/perl5/site_perl/5.8.8/i686-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/5.8.8/i686-linux /usr/lib/perl5/5.8.8 /usr/local/lib/site_perl) at /usr/sbin/pop-before-smtp line 172. BEGIN failed--compilation aborted at /usr/sbin/pop-before-smtp line 172. [ !! I resolved this by emerging perl-core/DB_File. Not sure if a use flag should be added and this be an optional dep or not.
$ equery b /usr/lib/perl5/5.8.8/i686-linux/DB_File.pm [ Searching for file(s) /usr/lib/perl5/5.8.8/i686-linux/DB_File.pm in *... ] dev-lang/perl-5.8.8-r2 (/usr/lib/perl5/5.8.8/i686-linux/DB_File.pm) Looks more like your perl is incomplete or you didn't run perl-cleaner ;) Anyway, the dependency should be virtual/perl-DB_File (not perl-core/DB_File)
Perl is complete on this server, but it was only a DNS server. The server recently became a mail server so I emerge mail related packages. qmail, courier-imap, pop-before-smtp. Also a ebuild I might add to portage, ASSP which is also in perl. So it's for sure a missing dep issue. I saw the virtual but was not sure if that's what the package should dep on or not. Again I think it depends on the format used for pop-before-smtp storage. I beleive one does not have to use DB, thus it might be some what optional. And why it has not been reported before. Although I must have run into this on 2 other servers that I run pop-before-smtp on. Will the ebuild be updated? If not I can modify the dep and commit to tree. Just did not want to step anyone's toes so I filled a but. Plus I would have dep'ed on a package, not the virtual. So I would have been wrong :)
Well, according to the above error, it's not much optional. I was just commenting on the fact that DB_File is a part of standard perl-5.8.8 install (that's why the virtual exists), so it's kinda weird that you are missing it. :)
Well keep in mind I am using db format for my pop-before-smtp stuff. That is something I had to configure and etc. I am not sure as to it's default out of the box. My gut says it does not use db format, otherwise whom ever made the ebuild would have included it as a dep. As for perl being incomplete no clue. Part of my reasoning for wanting a ebuild for the other perl application, ASSP, was so it could pull in all the deps. That one surely did, it pulled in a bunch of stuff for perl. Although I am pretty sure perl was already on this box in some minimal way. What ever would have brought it in for a base system + bind. Acutally vsftpd is also on this box, but never used, and is not off. Might remove it entirely. Anyway thanks for the info. If I get some time, I might look into why it was missing in case there is some other bug or etc.
posting the required emerge info would have resolved this quicker. betting there's a perl installed without the berkdb use flag enabled. The virtual for this module (virtal/perl-DB_File) has been updated to catch this now.
Yes, that is 100% correct. I recall the berkdb flag being enabled in a profile. I had to go around and set it specifically as a USE flag on several machines. This being primarily a dns server now converted to do more. Perl was present but the berkdb USE flag was not enabled. Sorry about the emerge info, it's been quite some time since I added that to a bug. Will do so for any future bug posts. Thanks and sorry for not including it from the start.
Closing, as I don't think anything else should be done here. Thanks, everyone.
