I've now made two releases (stdlib and luaposix) from my rockspec
template; let me know if you're happy, and I'll try to work out what
best to write up for the LuaRocks docs about integrating with GNU
autotools.
--
http://rrt.sc3d.org
-
On 16 September 2011 21:41, Hisham wrote:
>
> I just noticed that the same is not true in the luaposix configure
> script -- if you pass --libdir and --datadir, /lua/5.1 is
> automatically added.
I fixed this; it's no longer done.
> As it is, we can't use --libdir=$(LIBDIR)
> --datadir=$(LUADIR)
On Fri, Sep 16, 2011 at 5:25 PM, Hisham wrote:
> Also, my example above was slightly incorrect. As you can override the
> paths entirely, you need to add /lua/5.1 explicitly:
I just noticed that the same is not true in the luaposix configure
script -- if you pass --libdir and --datadir, /lua/5.1
On Fri, Sep 16, 2011 at 5:05 PM, Hisham wrote:
> On Fri, Sep 16, 2011 at 2:44 PM, Reuben Thomas wrote:
>> On Sep 16, 2011 4:52 PM, "Hisham" wrote:
>>>
>>
>>> LUADIR, like PREFIX, is generated based on the rockspec you are
>>> building. But do you really need to customize it? During the
>>> deplo
On Fri, Sep 16, 2011 at 5:36 PM, Reuben Thomas wrote:
> On 16 September 2011 21:25, Hisham wrote:
>>
>> I'm using uname, but I'm "normalizing" the received values a bit, as
>> some platforms tend to provide different results (for example, I spot
>> `elseif proc:match("amd64") or proc:match("x86_6
On 16 September 2011 21:25, Hisham wrote:
>
> I'm using uname, but I'm "normalizing" the received values a bit, as
> some platforms tend to provide different results (for example, I spot
> `elseif proc:match("amd64") or proc:match("x86_64") then proc =
> "x86_64"` in the code).
Why normalize? On
On Fri, Sep 16, 2011 at 5:09 PM, Reuben Thomas wrote:
> On 16 September 2011 21:05, Hisham wrote:
>>
>> You should be able to configure your luarocks/config.lua file with
>> something like:
>>
>> rocks_trees = {
>> {
>> root = home.."/local",
>> bin_dir = home.."/local/arch/bin",
>>
On 16 September 2011 21:05, Hisham wrote:
>
> You should be able to configure your luarocks/config.lua file with
> something like:
>
> rocks_trees = {
> {
> root = home.."/local",
> bin_dir = home.."/local/arch/bin",
> lib_dir = home.."/local/arch/lib",
> lua_dir = home.."/lo
On Fri, Sep 16, 2011 at 2:44 PM, Reuben Thomas wrote:
> On Sep 16, 2011 4:52 PM, "Hisham" wrote:
>>
>
>> LUADIR, like PREFIX, is generated based on the rockspec you are
>> building. But do you really need to customize it? During the
>> deployment phase, all files installed in LUADIR are moved to
On Sep 16, 2011 4:52 PM, "Hisham" wrote:
>
> LUADIR, like PREFIX, is generated based on the rockspec you are
> building. But do you really need to customize it? During the
> deployment phase, all files installed in LUADIR are moved to the
> proper $PREFIX/share/lua/5.1 (relative to the prefix of
On Fri, Sep 16, 2011 at 11:44 AM, Reuben Thomas wrote:
> On 16 September 2011 15:34, Reuben Thomas wrote:
>> On 15 September 2011 23:46, Reuben Thomas wrote:
>>> The one thing I can't see how to do after getting a working rockspec
>>> for both luaposix and stdlib is how to install .lua files in
On 16 September 2011 15:34, Reuben Thomas wrote:
> On 15 September 2011 23:46, Reuben Thomas wrote:
>> The one thing I can't see how to do after getting a working rockspec
>> for both luaposix and stdlib is how to install .lua files in a
>> different place from .so files. It's fairly common to in
On 15 September 2011 23:46, Reuben Thomas wrote:
> The one thing I can't see how to do after getting a working rockspec
> for both luaposix and stdlib is how to install .lua files in a
> different place from .so files. It's fairly common to install
> (arch-independent) .lua files once per system u
The one thing I can't see how to do after getting a working rockspec
for both luaposix and stdlib is how to install .lua files in a
different place from .so files. It's fairly common to install
(arch-independent) .lua files once per system under
/usr/local/share/lua/5.1 or similar, while .so files
Here's a first go at a luarock for luaposix 5.1.12:
package="luaposix"
version="5.1.12-1"
source = {
url = "http://luaforge.net/frs/download.php/4844/luaposix-5.1.12.tar.gz";,
md5 = "fcead5aa7d78b7d2c578e55177524aaa",
dir = "luaposix-5.1.12"
}
description = {
summary = "A POSIX library (in
On Mon, Sep 12, 2011 at 10:09 PM, Reuben Thomas wrote:
> On 12 September 2011 22:28, Hisham wrote:
>> On Mon, Sep 12, 2011 at 5:21 PM, Reuben Thomas wrote:
>>> Can I just use e.g. luarocks.path.bin_dir() in my rockspec to get this
>>> information? How? I don't see any examples...
>>
>> Take a lo
On 12 September 2011 22:28, Hisham wrote:
> On Mon, Sep 12, 2011 at 5:21 PM, Reuben Thomas wrote:
>> Can I just use e.g. luarocks.path.bin_dir() in my rockspec to get this
>> information? How? I don't see any examples...
>
> Take a look at this one:
>
> http://luarocks.org/repositories/rocks/lcur
On Mon, Sep 12, 2011 at 5:21 PM, Reuben Thomas wrote:
> Hi,
>
> I want to update the luarock for luaposix, which now has a GNU
> autotools-based build system. This should be pretty simple, I think,
> but I would like some guidance in case I'm trying to do it the wrong
> way.
>
> It would be nice t
Hi,
I want to update the luarock for luaposix, which now has a GNU
autotools-based build system. This should be pretty simple, I think,
but I would like some guidance in case I'm trying to do it the wrong
way.
It would be nice to add a new build type in the end, but since it
should be pretty simp
19 matches
Mail list logo
