diff options
author | Alejandro Pulver <alepulver@FreeBSD.org> | 2006-11-17 00:37:02 +0000 |
---|---|---|
committer | Alejandro Pulver <alepulver@FreeBSD.org> | 2006-11-17 00:37:02 +0000 |
commit | 11c8e83c7f2503c58fe6d465064900474535ab19 (patch) | |
tree | a7ec892a29edb89285aa204a1282203d79c31799 | |
parent | 35b4243ddd25921e1a0312c7a4f2b697cc458e96 (diff) |
Notes
-rw-r--r-- | en_US.ISO8859-1/books/porters-handbook/book.sgml | 35 |
1 files changed, 18 insertions, 17 deletions
diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml index cb2614270c..b9126d5709 100644 --- a/en_US.ISO8859-1/books/porters-handbook/book.sgml +++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml @@ -6770,12 +6770,12 @@ PLIST_SUB+= VERSION="${VER_STR}" <para>There are many versions of the <application>Lua</application> libraries and corresponding interpreters, which conflict between - them (install files under the same name). In the ports tree this + them (install files under the same name). In the ports tree this problem has been solved by installing each version under a different name using version number suffixes.</para> <para>The obvious disadvantage of this is that each application has to - be modified to found the expected version. But it can be solved by + be modified to find the expected version. But it can be solved by adding some additional flags to the compiler and linker.</para> </sect2> @@ -6823,7 +6823,7 @@ PLIST_SUB+= VERSION="${VER_STR}" </table> <para>The following is a list of available - <application>Lua</application> versions and the corresponding port + <application>Lua</application> versions and the corresponding ports in the tree:</para> <table frame="none"> @@ -6905,7 +6905,7 @@ PLIST_SUB+= VERSION="${VER_STR}" </table> <para>There are also some variables to select the preferred versions - from the available ones. They can be set to a list of versions, the + from the available ones. They can be set to a list of versions, the first ones will have higher priority.</para> <table frame="none"> @@ -6943,7 +6943,7 @@ PLIST_SUB+= VERSION="${VER_STR}" <para>The following fragment is from a port which can use <application>Lua</application> version <literal>5.0</literal> or <literal>5.1</literal>, and uses <literal>5.0</literal> by - default. It can be overriden by the user using + default. It can be overriden by the user using <makevar>WITH_LUA_VER</makevar>.</para> <programlisting>USE_LUA= 5.0-5.1 @@ -6955,9 +6955,10 @@ WANT_LUA_VER= 5.0</programlisting> <title>Component selection</title> <para>There are other applications that, while not being - <application>Lua</application> libraries, are related to them. These - applications can be specified in the <makevar>LUA_COMPS</makevar> - variable. The following components are available:</para> + <application>Lua</application> libraries, are related to them. + These applications can be specified in the + <makevar>LUA_COMPS</makevar> variable. The following components are + available:</para> <table frame="none"> <title>Available <application>Lua</application> components</title> @@ -7007,10 +7008,10 @@ WANT_LUA_VER= 5.0</programlisting> modules).</para> </note> - <para>The dependency type added when you select each component can be - manually specified by adding a suffix separated by a - <literal>:</literal>, or a default value will be used. The available - dependency types are:</para> + <para>The dependency type can be selected for each component by adding + a suffix separated by a semicolon. If not present then a default + type will be used (see <xref linkend="lua-def-dep-types">). The + following types are available:</para> <table frame="none"> <title>Available <application>Lua</application> dependency @@ -7053,7 +7054,7 @@ WANT_LUA_VER= 5.0</programlisting> <para>The default values for the components are detailed in the following table:</para> - <table frame="none"> + <table id="lua-def-dep-types" frame="none"> <title>Default <application>Lua</application> dependency types</title> @@ -7106,8 +7107,8 @@ LUA_COMPS= lua ruby</programlisting> <title>Detecting installed versions</title> <para>To detect an installed version you have to define - <makevar>WANT_LUA</makevar>. If you do not set it to a specific - version then the components will have a version suffix. The + <makevar>WANT_LUA</makevar>. If you do not set it to a specific + version then the components will have a version suffix. The <makevar>HAVE_LUA</makevar> variable will be filled after detection.</para> @@ -7150,8 +7151,8 @@ CONFIGURE_ARGS+=--enable-tolua <sect2 id="lua-defined-variables"> <title>Defined variables</title> - <para>The following variables are defined after defining one of the - variables from <xref linkend="lua-ver-sel-table">.</para> + <para>The following variables are available in the port (after + defining one from <xref linkend="lua-ver-sel-table">).</para> <table frame="none"> <title>Variables defined for ports that use |