Changeset 2da087bd for basicnet/netprogs/ncftp/ncftp-inst.xml

Timestamp:

09/17/2003 03:38:21 PM (21 years ago)

Author:

Larry Lawrence <larry@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.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, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

5bc2a01

Parents:

b152f10

Message:

update to ncftp-3.1.6

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

File:

• basicnet/netprogs/ncftp/ncftp-inst.xml (modified) (2 diffs)

basicnet/netprogs/ncftp/ncftp-inst.xml

@@ -1 +1 @@
 <sect2>
-<title>Installation of ncftp</title>
+<title>Installation of <application>ncftp</application></title>
 
-<para>There are two ways to build ncftp.  The first (and optimal) way,
-builds most of the functionality as a shared library and then builds and
-installs the program linked against this library.  The second method
-simply links all of the functionality into the binary statically.  This
+<para>There are two ways to build <application>ncftp</application>.  The first 
+(and optimal) way, builds most of the functionality as a shared library and 
+then builds and installs the program linked against this library.  The second 
+method simply links all of the functionality into the binary statically.  This
 doesn't make the dynamic library available for linking by other
 applications.  You need to choose which method best suits you.  Note
 that the second method does <emphasis>not</emphasis> create an entirely
-statically linked binary; only the libncftp parts are statically linked
-in, in this case. Be aware that building and using the shared library is 
-covered by the Clarified Artistic License; however, developing applications 
-that utilize the shared library is subject to a different license.</para>
+statically linked binary; only the <filename>libncftp</filename> parts are 
+statically linked in, in this case. Be aware that building and using the shared 
+library is covered by the Clarified Artistic License; however, developing 
+applications that utilize the shared library is subject to a different license.
+</para>
 
-<para>To install ncftp using the first (and optimal) method, run the 
-following commands:</para>
+<para>To install <application>ncftp</application> using the first (and optimal) 
+method, run the following commands:</para>
 
-<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
+<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
 cd libncftp &amp;&amp;
 make shared &amp;&amp;
@@ -23 +24 @@
 cd .. &amp;&amp;
 make &amp;&amp;
-make install</userinput></screen></para>
+make install</command></userinput></screen>
 
-<para>To install ncftp using the second method (with the libncftp 
-functionality linked in statically) run the following commands:</para>
+<para>To install <application>ncftp</application> using the second method (with 
+the <filename>libncftp</filename> functionality linked in statically) run the 
+following commands:</para>
 
-<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
+<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
 make &amp;&amp;
-make install</userinput></screen></para>
+make install</command></userinput></screen>
 
 </sect2>