Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jun 2019 15:20:00 +0000 (UTC)
From:      Mathieu Arnold <mat@FreeBSD.org>
To:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   svn commit: r504552 - in head/dns: bind9-devel/files bind911/files bind914/files
Message-ID:  <201906191520.x5JFK0WO079746@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: mat
Date: Wed Jun 19 15:20:00 2019
New Revision: 504552
URL: https://svnweb.freebsd.org/changeset/ports/504552

Log:
  Convert BIND9's pkg-message files to UCL.

Modified:
  head/dns/bind9-devel/files/pkg-message.in   (contents, props changed)
  head/dns/bind911/files/pkg-message.in   (contents, props changed)
  head/dns/bind914/files/pkg-message.in   (contents, props changed)

Modified: head/dns/bind9-devel/files/pkg-message.in
==============================================================================
--- head/dns/bind9-devel/files/pkg-message.in	Wed Jun 19 14:31:10 2019	(r504551)
+++ head/dns/bind9-devel/files/pkg-message.in	Wed Jun 19 15:20:00 2019	(r504552)
@@ -1,28 +1,29 @@
-**********************************************************************
-*            _  _____ _____ _____ _   _ _____ ___ ___  _   _         *
-*           / \|_   _|_   _| ____| \ | |_   _|_ _/ _ \| \ | |        *
-*          / _ \ | |   | | |  _| |  \| | | |  | | | | |  \| |        *
-*         / ___ \| |   | | | |___| |\  | | |  | | |_| | |\  |        *
-*        /_/   \_\_|   |_| |_____|_| \_| |_| |___\___/|_| \_|        *
-*                                                                    *
-*   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       *
-*                                                                    *
-*                                                                    *
-*   THIS IS A DEVELOPMENT VERSION OF BIND, IT WILL EAT YOUR DATA     *
-*                                                                    *
-*                                                                    *
-*                                                                    *
-**********************************************************************
+[
+{
+# %!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
+}
+{
+  message: <<EOT
++------------------------------------------------------------+
+|THIS IS A DEVELOPMENT VERSION OF BIND, IT WILL EAT YOUR DATA|
++------------------------------------------------------------+
+EOT
+}
+]

Modified: head/dns/bind911/files/pkg-message.in
==============================================================================
--- head/dns/bind911/files/pkg-message.in	Wed Jun 19 14:31:10 2019	(r504551)
+++ head/dns/bind911/files/pkg-message.in	Wed Jun 19 15:20:00 2019	(r504552)
@@ -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
+}
+]

Modified: head/dns/bind914/files/pkg-message.in
==============================================================================
--- head/dns/bind914/files/pkg-message.in	Wed Jun 19 14:31:10 2019	(r504551)
+++ head/dns/bind914/files/pkg-message.in	Wed Jun 19 15:20:00 2019	(r504552)
@@ -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
+}
+]



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906191520.x5JFK0WO079746>