Changeset d4277d4 for pst

Timestamp:

01/31/2006 04:24:01 AM (18 years ago)

Author:

Randy McMurchy <randy@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

4677cbc

Parents:

1080241

Message:

Removed the piping of 'yes' commands from the installation of the packages containing Sun license agreements (JDK binary, FOP and FreeTTS) and instead provided a note to reference the text about automating builds

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@5616 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• pst/ps/fop.xml (modified) (3 diffs)

pst/ps/fop.xml

@@ -129 +129 @@
       <title>Installing JAI</title>
 
+      <tip>
+        <para>The
+        <command>$FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin</command>
+        command below installs the JAI components in the JDK tree. You will be
+        required to view, and then accept (by entering a <keycap>y</keycap>
+        keypress), a license agreement before the installation will continue.
+        If you are scripting (automating) the build, you'll need to account for
+        this. There is information about automating build commands in the
+        <xref linkend="automating-builds"/> section of Chapter 2. Towards the
+        end of this section, specific information for automating this type of
+        installation is discussed.</para>
+      </tip>
+
       <para>Install the JAI components by running the following commands as
       the <systemitem class="username">root</systemitem> user while in the
@@ -138 +151 @@
 FOP_BUILD_DIR=$(pwd) &amp;&amp;
 cd $JAVA_HOME &amp;&amp;
-yes | $FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin &amp;&amp;
+$FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin &amp;&amp;
 cd $FOP_BUILD_DIR</userinput></screen>
 
@@ -250 +263 @@
     syntax.</para>
 
-    <para><command>yes | $FOP_BUILD_DIR/../jai-...-jdk.bin</command>: This
+    <para><command>$FOP_BUILD_DIR/../jai-...-jdk.bin</command>: This
     command installs the <application>JAI</application> components
-    into the <application>JDK</application> file structure. The
-    <command>yes</command> command is piped through so that you don't have to
-    scroll through four pages of the license agreement and automatically responds
-    <quote>yes</quote> to the agreement. <envar>$FOP_BUILD_DIR</envar> is used as
-    a reference point to the source executable and as a method to return back to
-    the <application>FOP</application> source tree.</para>
+    into the <application>JDK</application> file structure.
+    <envar>$FOP_BUILD_DIR</envar> is used as a reference point to the source
+    executable and as a method to return back to the
+    <application>FOP</application> source tree.</para>
 
     <para><command>sed -i "s/build/lib/" ...</command>: These commands modify