metasploit installs a new env file into: /etc/env.d/91metasploit the software won't run after the initial install because user must update env variables either by running env-update or relogining. Please add that note to the post-install message.
also, please swap the following two lines: elog "emerge --config postgresql-server" elog "/etc/init.d/postgresql-<version> start" The database must be up before running config.
(In reply to Anton Bolshakov from comment #1) > also, please swap the following two lines: > > elog "emerge --config postgresql-server" > elog "/etc/init.d/postgresql-<version> start" > > > The database must be up before running config. the postinst message for postgresql directly contradicts that. Also, my scripts for doing it contradict that. in a word, no.
ok, double check it. Because it contradicts with: pkg_config() { einfo "If the following fails, it is likely because you forgot to start/config postgresql first"
(In reply to Anton Bolshakov from comment #3) > ok, double check it. Because it contradicts with: > > pkg_config() { > einfo "If the following fails, it is likely because you forgot to > start/config postgresql first" no, it doesn't. Metasploit's pkg_config requires postgres to be started. postgres requires it's pkg_config to be run before it can be started. There are no contradictions in the metasploit postinst or config output. I am happy to accept suggestions for improvement, but as it stands now it is correct.
+ 17 Apr 2014; Rick Farina <zerochaos@gentoo.org> metasploit-4.9.2-r1.ebuild, + metasploit-9999.ebuild: + add elog command to warn user to update their env before running, bug #496720