The problem affects the two most recent ebuilds for mail-filter/maildrop currently present in Portage: 1.8.1-r2 and 2.0.1; older versions didn't depend on fam. The problem is that the section responsible for applying maildrop-1.8.0- db4.patch changes the directory to ${S}/bdbobj, making it impossible to correctly apply maildrop-1.8.1-disable-fam.patch in the next step. Attached you will find a patch which fixes this problem. It was created for 2.0. 1, but since the relevant part of the ebuild doesn't differ it should also be usable for 1.8.1-r2.
Created attachment 70785 [details, diff] maildrop-2.0.1.ebuild-cdS.patch
Sorry but I cannot reproduce this one. I successfully built both maildrop-1.8.1-r2 and maildrop-2.0.1 with USE="berkdb -fam". Does it fail for you or it is just a cosmetic change ? (I mean, the change makes sense anyway) Cheers, Ferdy
Alright it turns out that I need more caffeine... fixed in CVS (not bumped). Thanks Ferdy