aboutsummaryrefslogtreecommitdiff
path: root/doc/installation.html
diff options
context:
space:
mode:
authorDiego Nehab <diego@tecgraf.puc-rio.br>2006-04-20 04:16:23 +0000
committerDiego Nehab <diego@tecgraf.puc-rio.br>2006-04-20 04:16:23 +0000
commit75f51d5bc7367af6a52700db989499162e8525e8 (patch)
treec8b0c1b7c60130b6732ab3d5cabfb89d8566c7f9 /doc/installation.html
parent316e205cd4dea804b68ed6ca14cf8b41acf6712f (diff)
downloadluasocket-75f51d5bc7367af6a52700db989499162e8525e8.tar.gz
luasocket-75f51d5bc7367af6a52700db989499162e8525e8.tar.bz2
luasocket-75f51d5bc7367af6a52700db989499162e8525e8.zip
Almost ready to release 2.0.1
Diffstat (limited to 'doc/installation.html')
-rw-r--r--doc/installation.html32
1 files changed, 17 insertions, 15 deletions
diff --git a/doc/installation.html b/doc/installation.html
index 725db42..dadfe72 100644
--- a/doc/installation.html
+++ b/doc/installation.html
@@ -39,27 +39,24 @@ Installation">
39 39
40<h2>Installation</h2> 40<h2>Installation</h2>
41 41
42<p> LuaSocket 2.0.1 uses the new package proposal for Lua 5.1. 42<p> LuaSocket 2.0.1 uses the new package system for Lua 5.1.
43All Lua library developers are encouraged to update their libraries so that 43All Lua library developers are encouraged to update their libraries so that
44all libraries can coexist peacefully and users can benefit from the 44all libraries can coexist peacefully and users can benefit from the
45standardization and flexibility of the standard. 45standardization and flexibility of the standard.
46</p> 46</p>
47 47
48<p> 48<p>
49The proposal was considered important enough by some of us to justify 49Those stuck with Lua 5.0 will need the
50early adoption, even before release of Lua 5.1.
51Thus, a compatibility module
52<a href=http://www.keplerproject.org/compat/>compat-5.1</a> 50<a href=http://www.keplerproject.org/compat/>compat-5.1</a>
53has been released in conjunction with Roberto Ierusalimschy and <a 51module. It is maintained by
54href=http://www.keplerproject.org/>The Kepler Project</a> team. 52<a href=http://www.keplerproject.org/>The Kepler
55It implements the Lua 5.1 package proposal on top of Lua 5.0. </p> 53Project</a>'s team, and implements the Lua 5.1 package proposal
56 54on top of Lua 5.0. </p>
57<p> As far as LuaSocket is concerned, this means that whoever is 55
58deploying a non-standard distribution of LuaSocket will probably 56<p> Here we will only describe the standard distribution.
59have no problems customizing it. Here we will only describe the standard distribution. If the standard doesn't meet your 57If the standard doesn't meet your needs, we refer you to the
60needs, we refer you to the Lua discussion list, where any question about 58Lua discussion list, where any question about the package
61the package scheme will likely already have been answered. 59scheme will likely already have been answered. </p>
62</p>
63 60
64<h3>Directory structure</h3> 61<h3>Directory structure</h3>
65 62
@@ -88,7 +85,7 @@ distribution directory structure:</p>
88</pre> 85</pre>
89 86
90<p> Naturally, on Unix systems, <tt>core.dll</tt> 87<p> Naturally, on Unix systems, <tt>core.dll</tt>
91would be replaced by <tt>core.so</tt>. 88would be replaced by <tt>core.so</tt>.
92</p> 89</p>
93 90
94<p> In order for the interpreter to find all LuaSocket components, three 91<p> In order for the interpreter to find all LuaSocket components, three
@@ -100,6 +97,11 @@ LUA_INIT=@&lt;LDIR&gt;/compat-5.1.lua
100</pre> 97</pre>
101 98
102<p> 99<p>
100This is only need for Lua&nbsp;5.0! Lua&nbsp;5.1 comes with
101the package system bult in, of course.
102</p>
103
104<p>
103The other two environment variables instruct the compatibility module to 105The other two environment variables instruct the compatibility module to
104look for dynamic libraries and extension modules in the appropriate 106look for dynamic libraries and extension modules in the appropriate
105directories and with the appropriate filename extensions. 107directories and with the appropriate filename extensions.