net-im/openfire: fixup CONFIG_PROTECT handling in latest revision.

My -r2 accidentally clobbers the existing value of CONFIG_PROTECT
instead of appending to it. Oops. Fix it in place.

Signed-off-by: Michael Orlitzky <mjo@gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11

diff --git a/net-im/openfire/openfire-4.2.3-r2.ebuild b/net-im/openfire/openfire-4.2.3-r2.ebuild
index d504e403abae0d05dec957a76619341a417e31fd..dc79cda8b4ba225c8770b3ea69d1bb7fe2418f25 100644 (file)
--- a/net-im/openfire/openfire-4.2.3-r2.ebuild
+++ b/net-im/openfire/openfire-4.2.3-r2.ebuild
@@ -41,8 +41,7 @@ src_compile() {
 src_install() {
        #Protect ssl key on upgrade
        dodir /etc/env.d/
-       echo 'CONFIG_PROTECT="/opt/openfire/resources/security/"' > "${D}"/etc/env.d/98openfire
-       echo 'CONFIG_PROTECT="/opt/openfire/conf/"' > "${D}"/etc/env.d/98openfire
+       echo 'CONFIG_PROTECT="/opt/openfire/conf/ /opt/openfire/resources/security/"' > "${D}"/etc/env.d/98openfire
 
        newinitd "${FILESDIR}"/openfire-initd openfire
        newconfd "${FILESDIR}"/openfire-confd openfire