From 2737c2fd27c95bec49013e09f7f907c13c4e7596 Mon Sep 17 00:00:00 2001
From: Bruce Dubbs <bdubbs@linuxfromscratch.org>
Date: Mon, 30 Aug 2021 23:44:07 -0500
Subject: [PATCH] Update and tag tigervnc. The configuration instructions were
 not separated between sysv and systemd sufficiently.

---
 xsoft/other/tigervnc.xml | 27 +++++++++++++--------------
 1 file changed, 13 insertions(+), 14 deletions(-)

diff --git a/xsoft/other/tigervnc.xml b/xsoft/other/tigervnc.xml
index 5c489401c5..8e1819c33d 100644
--- a/xsoft/other/tigervnc.xml
+++ b/xsoft/other/tigervnc.xml
@@ -36,7 +36,7 @@
       viewing of the remote graphical desktop.
     </para>
 
-    &lfs101_checked;
+    &lfs110a_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
     <itemizedlist spacing="compact">
@@ -101,13 +101,13 @@
         <para>
           Optional files:
             <itemizedlist spacing="compact">
-              <listitem>
+              <listitem revision='sysv'>
                 <para><ulink url="&sources-anduin-http;/tigervnc/vncserver"/></para>
               </listitem>
-              <listitem>
+              <listitem revision='sysv'>
                 <para><ulink url="&sources-anduin-http;/tigervnc/vncserver.1"/></para>
               </listitem>
-              <listitem>
+              <listitem revision='systemd'>
                 <para><ulink url="&sources-anduin-http;/tigervnc/Xsession"/></para>
               </listitem>
             </itemizedlist>
@@ -260,7 +260,7 @@ ln -sfv tigervnc_24.png /usr/share/pixmaps/tigervnc.png</userinput></screen>
   <sect2 role="configuration">
     <title>Configuring Tigervnc</title>
 
-    <para>
+    <para revision='sysv'>
       The default installation of this package makes some changes in the way it
       is used.  The vncserver perl script is placed in /usr/libexec and the
       server is designed to be run via a systemd style .service file or the
@@ -269,15 +269,14 @@ ln -sfv tigervnc_24.png /usr/share/pixmaps/tigervnc.png</userinput></screen>
       manager to be installed.
     </para>
 
-    <para>
+    <para revision='sysv'>
+      To restore the previous behavior, install the additional downloaded
+      files as the <systemitem class="username">root</systemitem> user:</para>
 
-      To restore the previous behavior, as the <systemitem
-      class="username">root</systemitem> user:</para>
-
-<screen role="nodump"><userinput>install -m755 --owner=root ../vncserver /usr/bin &amp;&amp;
+<screen role="nodump" revision='sysv'><userinput>install -m755 --owner=root ../vncserver /usr/bin &amp;&amp;
 cp ../vncserver.1 /usr/share/man/man1</userinput></screen>
 
-    <para>
+    <para revision='sysv'>
       Using the previous procedures, the user specific configuration files of
       vncserver reside in the <filename class='directory'>.vnc</filename>
       directory in the user's home directory.  The
@@ -288,18 +287,18 @@ cp ../vncserver.1 /usr/share/man/man1</userinput></screen>
       <filename>xstartup</filename> would be:
     </para>
 
-<screen>#!/bin/sh
+<screen revision='sysv'>#!/bin/sh
 [ -x /etc/vnc/xstartup ] &amp;&amp; exec /etc/vnc/xstartup
 [ -r $HOME/.Xresources ] &amp;&amp; xrdb $HOME/.Xresources
 startlxde &amp;</screen>
 
-    <para>
+    <para revision='sysv'>
       The <filename>xstartup</filename> file must be executable for the
       commands in it to be executed, so run <command>chmod a+x
       ~/.vnc/xstartup</command>.
     </para>
 
-    <para>
+    <para revision='sysv'>
       Set up the vnc passwd with <command>vncpasswd</command>. The
       server can then be started with the <command>vncserver</command>
       command.