There is a postinst message in mail-client/claws-mail that suggests running /bin/bash /usr/portage/mail-client/claws-mail/files/plugins-rebuild.sh. It worked fine until sys-apps/portage was upgraded to 2.2_rc40 version. Now I get this: Looking for claws-mail plugins to rebuild ... /usr/portage/mail-client/claws-mail/files/plugins-rebuild.sh: line 30: /usr/lib/portage/bin/pkgname: No such file or directory Found plugins for rebuilding: Rebuilding with given emerge options: emerge: the other white meat (command-line interface to the Portage system) Usage: emerge [ options ] [ action ] [ ebuild | tbz2 | file | @set | atom ] [ ... ] emerge [ options ] [ action ] < system | world > emerge < --sync | --metadata | --info > emerge --resume [ --pretend | --ask | --skipfirst ] emerge --help [ --verbose ] Options: -[abBcCdDefgGhjkKlnNoOpqPsStuvV] [ --color < y | n > ] [ --columns ] [ --complete-graph ] [ --deep ] [ --jobs JOBS ] [ --keep-going ] [ --load-average LOAD ] [ --newuse ] [ --noconfmem ] [ --nospinner ] [ --oneshot ] [ --onlydeps ] [ --reinstall changed-use ] [ --with-bdeps < y | n > ] Actions: [ --depclean | --list-sets | --search | --sync | --version ] For more help try 'emerge --help --verbose' or consult the man page. No plugins found. The problem is obviously is absence of /usr/lib/portage/bin/pkgname in latest portage.
Ok, I did not write that script, so I have to investigate a bit. Stay tuned.
claws-mail ebuild also detects installed plugins, but it simply uses pre-defined list of available plugins (as opposed to looking in /var/db/pkg). Maybe ebuild and this script should be unified somehow.
I decided to remove the script alltogether and only keep a message in postinst...searching the vdb directly is a bad idea, anyway and rewriting the script is not worth the gain. Anyway, thank you for your report.
