Convert BIND9's pkg-message files to UCL.

1 files changed, 22 insertions, 23 deletions

diff --git a/dns/bind911/files/pkg-message.in b/dns/bind911/files/pkg-message.in
index a1bfad91fb81..1150a96522ff 100644
--- a/dns/bind911/files/pkg-message.in
+++ b/dns/bind911/files/pkg-message.in
@@ -1,23 +1,22 @@
-**********************************************************************
-*            _  _____ _____ _____ _   _ _____ ___ ___  _   _         *
-*           / \|_   _|_   _| ____| \ | |_   _|_ _/ _ \| \ | |        *
-*          / _ \ | |   | | |  _| |  \| | | |  | | | | |  \| |        *
-*         / ___ \| |   | | | |___| |\  | | |  | | |_| | |\  |        *
-*        /_/   \_\_|   |_| |_____|_| \_| |_| |___\___/|_| \_|        *
-*                                                                    *
-*   BIND requires configuration of rndc, including a "secret" key.   *
-*    The easiest, and most secure way to configure rndc is to run    *
-*   'rndc-confgen -a' to generate the proper conf file, with a new   *
-*            random key, and appropriate file permissions.           *
-*                                                                    *
-*     The %%PREFIX%%/etc/rc.d/named script will do that for you.     *
-*                                                                    *
-*      If using syslog to log the BIND9 activity, and using a        *
-*     chroot'ed installation, you will need to tell syslog to        *
-*       install a log socket in the BIND9 chroot by running:         *
-*                                                                    *
-*            # sysrc altlog_proglist+=named                          *
-*                                                                    *
-*    And then restarting syslogd with: service syslogd restart       *
-*                                                                    *
-**********************************************************************
+[
+{
+# %!fmt 59 63
+  message: <<EOT
+BIND requires configuration of rndc, including a "secret"
+key.  The easiest, and most secure way to configure rndc is
+to run 'rndc-confgen -a' to generate the proper conf file,
+with a new random key, and appropriate file permissions.
+
+The %%PREFIX%%/etc/rc.d/named script will do that for you.
+
+If using syslog to log the BIND9 activity, and using a
+chroot'ed installation, you will need to tell syslog to install
+a log socket in the BIND9 chroot by running:
+
+  # sysrc altlog_proglist+=named
+
+And then restarting syslogd with: service syslogd restart
+EOT
+  type: install
+}
+]