Changeset d4277d4
- Timestamp:
- 01/31/2006 04:24:01 AM (18 years ago)
- 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
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
general.ent
r1080241 rd4277d4 1 <!ENTITY day "3 0">1 <!ENTITY day "31"> 2 2 <!ENTITY month "01"> 3 3 <!ENTITY year "2006"> 4 4 <!ENTITY version "svn-&year;&month;&day;"> 5 <!ENTITY releasedate "January &day; th, &year;">5 <!ENTITY releasedate "January &day;st, &year;"> 6 6 <!ENTITY pubdate "&year;-&month;-&day;"> <!-- metadata req. by TLDP --> 7 7 <!ENTITY blfs-version "svn"> <!-- svn|[release #] --> -
general/prog/jdk.xml
r1080241 rd4277d4 83 83 84 84 <!-- Commented out right now as there is no md5sums file on Anduin 85 86 85 <listitem> 87 86 <para>Download MD5 sum (source): <ulink url="&jdk-source-md5sum;"/></para> 88 87 </listitem> 89 90 88 --> 91 89 … … 169 167 either or both.</para> 170 168 169 <tip> 170 <para>The <command>./jdk-&jdk-bin-string;-linux-i?86.bin</command> 171 command below unpacks the distribution into a 172 <filename class='directory'>jdk&jdk-bin-version;</filename> directory. 173 You will be required to view, and then accept (by entering a 174 <keycap>y</keycap> keypress), a license agreement before any files are 175 unpacked. If you are scripting (automating) the build, you'll need to 176 account for this. There is information about automating build commands 177 in the <xref linkend="automating-builds"/> section of Chapter 2. Towards 178 the end of this section, specific information for automating this type of 179 installation is discussed.</para> 180 </tip> 181 171 182 <para>Install the precompiled <application>JDK</application> with the 172 183 following commands:</para> … … 174 185 <screen><userinput>sed -i "s:^PATH=.*::" jdk-&jdk-bin-string;-linux-i?86.bin && 175 186 chmod -v +x jdk-&jdk-bin-string;-linux-i?86.bin && 176 mkdir -v -p bin && 177 ln -v -sf /bin/true bin/more && 178 yes | PATH=$PWD/bin:$PATH ./jdk-&jdk-bin-string;-linux-i?86.bin && 187 ./jdk-&jdk-bin-string;-linux-i?86.bin && 179 188 cd jdk&jdk-bin-version;</userinput></screen> 180 189 -
introduction/welcome/changelog.xml
r1080241 rd4277d4 43 43 44 44 <listitem> 45 <para>January 31st, 2006</para> 46 <itemizedlist> 47 <listitem> 48 <para>[randy] - Removed the piping of 'yes' commands from the 49 installation of the packages containing Sun license agreements 50 (JDK binary, FOP and FreeTTS) and instead provided a note to 51 reference the text about automating builds.</para> 52 </listitem> 53 </itemizedlist> 54 </listitem> 55 56 <listitem> 45 57 <para>January 30th, 2006</para> 46 58 <itemizedlist> -
multimedia/audioutils/freetts.xml
r1080241 rd4277d4 110 110 -x {META-INF/*,freetts-&freetts-version;/{acknowledgments.txt,license.terms}}</userinput></screen> 111 111 112 <tip> 113 <para>The <command>sh jsapi.sh</command> command below installs the Java 114 Speech API components into the <application>FreeTTS</application> source 115 tree. You will be required to view, and then accept (by entering a 116 <keycap>y</keycap> keypress), a license agreement before the installation 117 will continue. If you are scripting (automating) the build, you'll need 118 to account for this. There is information about automating build commands 119 in the <xref linkend="automating-builds"/> section of Chapter 2. Towards 120 the end of this section, specific information for automating this type of 121 installation is discussed.</para> 122 </tip> 123 112 124 <para>Install <application>FreeTTS</application> by running the following 113 125 commands:</para> 114 126 115 127 <screen><userinput>cd lib && 116 yes |sh jsapi.sh &&128 sh jsapi.sh && 117 129 cd .. && 118 130 ant</userinput></screen> … … 151 163 <title>Command Explanations</title> 152 164 153 <para><command>yes | sh jsapi.sh</command>: This command installs the 154 <application>Java Speech API</application> into the 155 <application>FreeTTS</application> source tree. <command>yes</command> 156 is piped so that this command can be scripted and will automatically 157 agree to the JSAPI license terms. You can view the license you are 158 agreeing to at 159 <ulink url="&files-anduin;/jsapi-license.txt"/>.</para> 165 <para><command>sh jsapi.sh</command>: This command installs the 166 <application>Java Speech API</application> components into the 167 <application>FreeTTS</application> source tree.</para> 160 168 161 169 <para><command>ant</command>: <application>FreeTTS</application> uses the -
pst/ps/fop.xml
r1080241 rd4277d4 129 129 <title>Installing JAI</title> 130 130 131 <tip> 132 <para>The 133 <command>$FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin</command> 134 command below installs the JAI components in the JDK tree. You will be 135 required to view, and then accept (by entering a <keycap>y</keycap> 136 keypress), a license agreement before the installation will continue. 137 If you are scripting (automating) the build, you'll need to account for 138 this. There is information about automating build commands in the 139 <xref linkend="automating-builds"/> section of Chapter 2. Towards the 140 end of this section, specific information for automating this type of 141 installation is discussed.</para> 142 </tip> 143 131 144 <para>Install the JAI components by running the following commands as 132 145 the <systemitem class="username">root</systemitem> user while in the … … 138 151 FOP_BUILD_DIR=$(pwd) && 139 152 cd $JAVA_HOME && 140 yes |$FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin &&153 $FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin && 141 154 cd $FOP_BUILD_DIR</userinput></screen> 142 155 … … 250 263 syntax.</para> 251 264 252 <para><command> yes |$FOP_BUILD_DIR/../jai-...-jdk.bin</command>: This265 <para><command>$FOP_BUILD_DIR/../jai-...-jdk.bin</command>: This 253 266 command installs the <application>JAI</application> components 254 into the <application>JDK</application> file structure. The 255 <command>yes</command> command is piped through so that you don't have to 256 scroll through four pages of the license agreement and automatically responds 257 <quote>yes</quote> to the agreement. <envar>$FOP_BUILD_DIR</envar> is used as 258 a reference point to the source executable and as a method to return back to 259 the <application>FOP</application> source tree.</para> 267 into the <application>JDK</application> file structure. 268 <envar>$FOP_BUILD_DIR</envar> is used as a reference point to the source 269 executable and as a method to return back to the 270 <application>FOP</application> source tree.</para> 260 271 261 272 <para><command>sed -i "s/build/lib/" ...</command>: These commands modify
Note:
See TracChangeset
for help on using the changeset viewer.