Am 15.05.2017 um 06:55 schröbte Russell Haley:
> Hi LuaRocks community,
Hi!
>
> I am looking at creating a Windows MSI installer for a click-and-go
> PUC-Lua package and I wanted to include LuaRocks. I looked at the
> installer (wonderful work by the way) and it seems to do some registry
> stuffs
Am 13.11.2016 um 19:07 schröbte Doug Currie:
I'm looking for help to construct an appropriate rockspec for an updated
lsqlite3.
lsqlite3-0.9.4-1.rockspec is uploaded to luarocks.org, and works on OS X
and Debian Linux. It fails on Windows.
Since 0.9.3, I've added a second module to lsqlite3 cal
Am 16.05.2016 um 16:17 schröbte Hisham:
> On 13 May 2016 at 11:57, Philipp Janda wrote:
>>
>> Having `build.modules` is actually rather nice, because you can infer
>> which modules are part of a rock without downloading the source code. I
>> think someone somewhere
Am 12.05.2016 um 22:09 schröbte Hisham:
>
> Waiting for your feedback,
> Hisham
>
> Streamlining the rockspec format
>
>
> if build.type is not given, assume builtin.
>
> If build.modules is not given:
Having `build.modules` is actually rather nice, because you can
Am 22.12.2015 um 01:08 schröbte Geoff Leyland:
> On 22/12/2015, at 12:05 pm, Philipp Janda wrote:
>>
>>> If I'm going to try do this, then there's a couple of other things that
>>> come to mind:
>>> - even LR3 doesn't seem to have a git_ssh
Am 21.12.2015 um 19:54 schröbte Geoff Leyland:
>> On 22/12/2015, at 1:33 am, Philipp Janda wrote:
>>
>> Two other things: This would probably be a welcome addition to LuaRocks3
>> (unfortunately the change isn't backwards compatible), and you can
>> impleme
Am 21.12.2015 um 13:15 schröbte Philipp Janda:
> Am 21.12.2015 um 12:14 schröbte Geoff Leyland:
>>> On 21/12/2015, at 11:26 pm, Daurnimator wrote:
>>>
>>> On 21 December 2015 at 19:37, Geoff Leyland
>>> wrote:
>>>> 2) There doesn'
Am 21.12.2015 um 12:14 schröbte Geoff Leyland:
>> On 21/12/2015, at 11:26 pm, Daurnimator wrote:
>>
>> On 21 December 2015 at 19:37, Geoff Leyland
>> wrote:
>>> 2) There doesn't seem to be a protocol on which luarocks will talk to a
>>> *private* repository on bitbucket.
>>> git:// seems to be
Am 14.09.2015 um 12:29 schröbte Gary V. Vaughan:
> Hi,
Hi!
>
> Yes, setting MACOSX_DEPLOYMENT_TARGET is a good idea, or else the resulting
> library
> *may* depend on system library symbols not available in releases prior to the
> one you
> compile on.
>
> There's no need to split it into two c
Am 10.09.2015 um 22:44 schröbte Reuben Thomas:
> A user just reported that my cw rock needs automake to build. I'm not sure
> why this hadn't struck me before!
>
> The problem, within luarocks, is that there's no way to express this
> dependency.
>
> Is there any standard way to address these sort
Am 26.03.2015 um 04:09 schröbte Hisham:
>
> [...]
>
> We have some design options, see below: (commands that don't hit the
> network are marked "[no network op]")
>
> Option a: add an 'upgrade' command. (Cue people asking for `upgrade
> --all` in 3...2...1...)
>
> $ luarocks show foo --mversion
> 1
Hi!
I would like to make a new rock for lhf's lbci library. May I have the
lbci module ownership be transfered from the "luarocks" account to my
account ("siffiejoe"), please?
Thx,
Philipp
--
Don't Limit Your Busines
Am 09.06.2015 um 17:22 schröbte Dimitris Papavasiliou:
> Hi,
Hi!
>
> I'm trying to package a REPL through LuaRocks which is available, both
> as a loadable module and as an executable script, which used said module
> to provide a standalone enhanced Lua prompt.
>
> Thanks to some input from the l
Am 27.05.2015 um 01:41 schröbte XIAO Qi:
> 2015-05-26 2:39 GMT+02:00 Philipp Janda :
>>
>> You already mentioned unit tests (or system tests), and I see that the
>> GSoC page also lists automatic documentation generation using tools like
>> LDoc, lut, Docco, Doxygen,
Am 26.05.2015 um 00:47 schröbte XIAO Qi:
> Hi all,
Hi!
>
> 1) As a rock developer, what kind of addons would you like to have?
>
> 2) As a prospective addon developer, which parts of LuaRocks should be
> available to plug into?
>
> As an example, say as a rock developer, I wish to have addons tha
Am 08.03.2015 um 22:46 schröbte Geoff Leyland:
> Hi,
>
> I thought I had seen somewhere that it was possible to put a URL in a
> rockspec’s dependencies, for example:
>
> dependencies = {
> "https://raw.githubusercontent.com/geoffleyland/lua-csv/master/rockspecs/csv-scm-1.rockspec”
> }
>
You ha
Hi!
Could someone with access to the `luarocks` user on Moonrocks please
upload this updated rockspec for luasocket? It adds the
`LUA_COMPAT_APIINTCASTS` define which at the moment is needed for
luasocket to work on Lua 5.3.
Thanks,
Philipp
package = "LuaSocket"
version = "3.0rc1-2"
source
Am 12.01.2015 um 23:23 schröbte Andrew Starks:
>
> It appears that there are many places where paths are generated and
> saved as literal values and that this is done on purpose. It's not
> what I would have expected and it prompted me to toss out a hasty
> email. :)
First we use the absolute path
Hi!
Am 12.01.2015 um 13:01 schröbte Thijs Schreijer:
>
> First try it complains about the .dll not being found. But as the dir listing
> shows, they are in c:\external\bin
The linker would find them if they were in `C:\external\lib`.
> In the second try, I explicitly point OPENSSL_LIBDIR into t
Am 23.12.2014 um 06:38 schröbte Vadim Peretokin:
> Hi,
>
Hi!
>
> The Lua mailing lists suggests that it is a compilation issue - the binary
> for 5.1 needs to be recompiled for 5.2 - but luarocks downloads the source
> and compiles that, so this shouldn't be the case. "luarocks" also reports
> it
Am 05.11.2014 um 16:00 schröbte Gerhard Preuss:
> Hi!
Hi!
>
>
> $ brew update
> $ brew upgrade
> $ brew install luarocks
> $ brew sh
> $ sudo luarocks install luasocket
>
> export MACOSX_DEPLOYMENT_TARGET=10.5; gcc -O2 -fPIC
> -I/usr/local/opt/lua/include -c src/buffer.c -o src/b
Am 17.10.2014 um 14:15 schröbte
alexandre.bertr...@tudor.lu:
> Hi Thijs, Philipp and Tomas,
Hi!
>
> So far I believe I solved the problem, which I had first thought about and
> the 3 of you confirmed it (thanks). Actually, I did an manual update of
> luarocks (from an old version 2.0.2 to newest
Am 16.10.2014 um 22:26 schröbte Thijs Schreijer:
>
>> -Original Message-
>> From: Philipp Janda [mailto:siffie...@gmx.net]
>> Sent: donderdag 16 oktober 2014 14:40
>> To: luarocks-developers@lists.sourceforge.net
>> Subject: Re: [Luarocks-developers] Pro
Am 16.10.2014 um 11:36 schröbte
alexandre.bertr...@tudor.lu:
> Hi Philipp,
Hi!
> thanks for the tip, that was my error. I still encountered 2 problems
> (described here: https://github.com/keplerproject/luafilesystem/issues/22
> and here http://comments.gmane.org/gmane.comp.lang.lua.luarocks/429
Am 15.10.2014 um 17:02 schröbte
alexandre.bertr...@tudor.lu:
> Hi Philipp,
Hi!
> many thanks for your help. Unfortunately, after I've downloaded both
> luasql-postgres-2.3.0.1-1.rockspec and luasql-postgres-2.3.0.1-1.src.rock
> files and used
>
> luarocks install luasql-postgres-2.3.0.1-1.src.ro
Am 14.10.2014 um 13:41 schröbte
alexandre.bertr...@tudor.lu:
> Hi,
Hi!
> I'm glad that I've started what seems to be an interesting discussion.
> Unfortunately, as I'm no developer, I must admit that I've no clue on how
> to (if I even can) adapt the code with any of the suggestions discussed.
Am 13.10.2014 um 17:10 schröbte Daurnimator:
> On 10 October 2014 18:43, Philipp Janda wrote:
>
>>
>> Not if you do it right from the beginning. Having programmed in C++
>> usually helps, because you have a clear idea of object ownership, and
>> Lua errors in comb
Am 10.10.2014 um 20:50 schröbte Hisham:
> On 10 October 2014 15:20, Tomas Guisasola Gorham
> wrote:
>> Hi Hisham and Philipp
Hi!
>>
>> I am not sure the pull request is a safe implementation since
>> an error (not enough memory?) could occur after the malloc and before
>> the f
Hi!
Am 10.10.2014 um 16:51 schröbte
alexandre.bertr...@tudor.lu:
>
> ls_postgres.c
> src/ls_postgres.c(374) : error C2057: expected constant expression
> src/ls_postgres.c(374) : error C2466: cannot allocate an array of constant
> size
> 0
> src/ls_postgres.c(374) : error C2133: 'to' : unknown si
Am 29.09.2014 um 13:07 schröbte Philipp Janda:
>
> I'm not sure installing LuaRocks as a rock is officially supported on
> Windows [...]
Sorry for the noise. Despite all the hints I assumed a Windows operating
system for some re
Am 29.09.2014 um 05:54 schröbte Daurnimator:
>
> You can get a local luarocks installation up by doing:
> $ /usr/bin/luarocks --local install luarocks
> This will give you a `luarocks` shell script at
> `$HOME/.luarocks/bin/luarocks`.
I'm not sure installing LuaRocks as a rock is officially suppor
Am 23.09.2014 um 21:13 schröbte Hisham:
> On 23 September 2014 04:44, Gunnar Zötl wrote:
>> Hi,
>>
>> thanks for the suggestions (and corrections).
>>
>>> 1) You mention `LUA_LIBDIR` but not `LUALIB`, which is the file name of
>>> the Lua library. If you need one, you probably need the other as we
Am 22.09.2014 um 17:51 schröbte Hisham:
> On 22 September 2014 12:27, Philipp Janda wrote:
>>
>> 1) You mention `LUA_LIBDIR` but not `LUALIB`, which is the file name of
>> the Lua library. If you need one, you probably need the other as well
>> (on Linux, *BSD, ..., yo
Am 22.09.2014 um 16:32 schröbte Gunnar Zötl:
>
>> Feel free to add to the wiki! Post a link here when you're done, then
>> everyone will be able to review and contribute to it.
>
> I did. The page is available at
>
> http://luarocks.org/en/Creating_a_Makefile_that_plays_nice_with_LuaRocks
>
> If I'
Am 01.09.2014 um 22:50 schröbte Hisham:
> On 28 August 2014 06:23, Philipp Janda wrote:
>>
>> It's LIBDIR that you want. Install there and let LuaRocks handle the
>> rest (i.e. copy the installed files to the usual locations). This way it
>> can keep track of what
Am 30.08.2014 um 01:13 schröbte Steven Degutis:
> I can't for the life of me figure this out.
>
> Here's the module I'm trying to convert:
> https://github.com/mjolnir-io/mjolnir-keycodes
>
> Basically it's a really simple module. The only strange things it
> needs are `CFLAGS += -fobjc-arc -Wall -
Am 28.08.2014 um 10:33 schröbte Gunnar Zötl:
> Hmmm ok. But then, from the wiki I gather that LUA_LIBDIR should actually be
> the
> path where I find the lua libs, like liblua.a? Like LUA_INCDIR and LUA_BINDIR
> are the paths where I find the relevant includes and binaries. Plus,
> LUA_LIBDIR
> d
Am 23.08.2014 um 09:52 schröbte Thijs Schreijer:
>
>
>> -Original Message-----
>> From: Philipp Janda [mailto:siffie...@gmx.net]
>> Sent: zaterdag 23 augustus 2014 2:05
>> To: luarocks-developers@lists.sourceforge.net
>> Subject: Re: [Luarocks-developers] ex
Am 23.08.2014 um 01:17 schröbte Thijs Schreijer:
> Building LuaSec on windows gives me;
>
> Installing https://rocks.moonscript.org/luasec-0.5-2.src.rock...
> Using https://rocks.moonscript.org/luasec-0.5-2.src.rock... switching to
> 'build' mode
> mingw32-gcc -O2 -c -o src/x509.o -IC:/Program Fil
Am 16.08.2014 um 14:17 schrieb Rafiq Mulla:
> Hi Team,
Hi!
>
> * /opt/local/share/lua/5.2/luarocks/command_line.lua:154: in function
> 'run_command'*
> * /usr/local/bin/luarocks:28: in main chunk*
My guess is that you are mixing two different installations/versions of
LuaRocks, one in `/opt/loc
Am 12.08.2014 um 20:47 schrieb RJP Computing:
> On Tue, Aug 12, 2014 at 11:38 AM, Philipp Janda wrote:
>
>> Am 12.08.2014 um 16:37 schrieb Ryan Pusztai:
>>> LuaLogging 1.3.0-1 fails to unpack or install on Ubuntu 14.04 amd64.
>>>
>>> I run `luarocks install
Am 12.08.2014 um 16:37 schrieb Ryan Pusztai:
> LuaLogging 1.3.0-1 fails to unpack or install on Ubuntu 14.04 amd64.
>
> I run `luarocks install lualogging` and get
> ```
> $ sudo luarocks install lualogging
> Installing
> http://luarocks.org/repositories/rocks/lualogging-1.3.0-1.src.rock...
> Using
Am 09.07.2014 21:34 schröbte Ignacio Burgueño:
> Hi everyone!
Hi!
>
> I have a rockspec which uses the builtin backend to build a simple module.
> I'd like to pass a flag to gcc (-fvisibility=hidden) but I don't know how
> (if possible). Did go through the docs and the code already, but nothing
>
Am 02.06.2014 18:37 schröbte Philipp Janda:
>
> AFAICT, adding --with-lua=/usr should work for all listed combinations
> (assuming all debs install into (`/usr/bin`). But I haven't tested ...
One more thing: You are supposed to do
make build && sudo make insta
Am 02.06.2014 17:26 schröbte Ignacio Burgueño:
> Hi
Hi!
>
> I have some automated testing on Travis-Ci using code I took from Alexey
> Melnichuk
> https://github.com/moteus
>
> Currently I'm testing using LR 2.1.1. I'd like to upgrade, but the
> ./configure step gives me an error.
>
> This is wit
Am 26.05.2014 13:49 schröbte Thijs Schreijer:
> Maybe best to add as a request to the issue tracker? [1] as it breaks
> rockspec compatibility, it can then be tagged as a possible 3.0 feature.
Most of the proposal doesn't break rockspec compatibility: Some Rocks
already install static libraries
Am 26.02.2014 19:06 schröbte Philipp Janda:
>
> I will look into it, but as a temporary measure you can try with LuaZip
> uninstalled (or removed/renamed) ...
>
Ok, the reason seems to be that the luajson .src.rock doesn't contain
explicit subdirectories in the zip file, so ex
Am 26.02.2014 17:55 schröbte RJP Computing:
> On Wed, Feb 26, 2014 at 11:05 AM, Philipp Janda wrote:
>>
>> For the record, I have successfully installed luajson-1.3.2-1 on Ubuntu
>> 13.10 x86_64 a few minutes ago.
>>
>
> That is good to know
>
>
>
Am 26.02.2014 16:08 schröbte RJP Computing:
>
> Here is "sudo luarocks --verbose install luajson"
>
>> $ sudo luarocks --verbose install luajson
>> Installing
>> http://www.luarocks.org/repositories/rocks/luajson-1.3.2-1.src.rock...
>> Using http://www.luarocks.org/repositories/rocks/luajson-1.3.2-
Am 31.01.2014 11:06 schröbte Gary V. Vaughan:
> Hi Philipp,
Hi!
>
> On Jan 31, 2014, at 11:15 AM, Philipp Janda wrote:
>
>> Am 30.01.2014 16:40 schröbte Hisham:
>>> On 30 January 2014 07:30, Gary V. Vaughan wrote:
>>>> Hi Hisham,
>>>>
>>
Am 31.01.2014 02:06 schröbte Hisham:
>
> They are ASCII-text that need a particular application to render that
> are not as ubiquitous as web browsers are and that we can't easily
> reuse in both offline and online documentation without some
> conversion.
If you want online documentation (as in WW
Am 30.01.2014 23:35 schröbte Hisham:
> On 30 January 2014 20:15, Philipp Janda wrote:
>> Am 30.01.2014 16:40 schröbte Hisham:
>>> On 30 January 2014 07:30, Gary V. Vaughan wrote:
>>>> Hi Hisham,
>>>>
>>>> In principle, would you accept a p
Am 30.01.2014 16:40 schröbte Hisham:
> On 30 January 2014 07:30, Gary V. Vaughan wrote:
>> Hi Hisham,
>>
>> In principle, would you accept a pull request if I did the work (though I
>> know the internals of LuaRocks almost not at all, so I might need some
>> pointers and a bit of help here and t
Am 17.01.2014 12:00 schröbte Alexey Melnichuk:
>
> Also I just get error while installing LuaRocks 2.1.2 with LuaJIT [1]
>
> # ./configure --lua-suffix=jit
> --with-lua-include=/usr/local/include/luajit-2.0
> # make && sudo make install
>
>> luajit not found in $PATH.
I believe that is because of
Am 16.01.2014 20:29 schröbte Geoff Leyland:
> Hi,
>
>[...]
>
> I’m afraid it’s LuaJIT only at the moment, it uses the FFI rather
> than the classic Lua API. If there’s interest I’ll try to find time
> to build a standard Lua binding. Furthermore, it uses a callback
> interface, like readosm, rather
Am 10.01.2014 20:26 schröbte Hisham:
> Hello list!
>
Hi!
>
> As usual, see the GitHub logs for detailed history and credits. And as
> always, all kind of feedback is much appreciated.
* the version number still says 2.1.1
* `doc.lua` is not installed by the Makefile (it's missing from
`LUAR
Am 09.01.2014 22:32 schröbte Hisham:
> On 9 January 2014 12:43, Philipp Janda wrote:.
>>
>> No need for a new ticket, the bug got fixed a few month ago in the
>> master branch (the current git HEAD works fine). But the bug is present
>> in the latest released luarocks v
Am 08.01.2014 17:21 schröbte Hisham:
> On 8 January 2014 13:56, Philipp Janda wrote:
>> Am 08.01.2014 16:30 schröbte Wouter Scherphof:
>>> this helped, thanks!
>>> should I report it as a bug somewhere?
>>
>> You can open a ticket here[1], but Hisham
Am 08.01.2014 16:30 schröbte Wouter Scherphof:
> this helped, thanks!
> should I report it as a bug somewhere?
You can open a ticket here[1], but Hisham usually also reads this
mailing list ...
Philipp
[1]: https://github.com/keplerproject/luarocks/issues
>
>
> 2014/1/
Hi!
Am 08.01.2014 06:39 schröbte Wouter Scherphof:
> Uhm, no, 5.2 actually.
I can confirm the problem.
Look at the modification date and/or contents of
`~/.cache/luarocks/http___www.luarocks.org_repositories_rocks/manifest-5.2`.
Mine was from 2013/10/28 and didn't list the newer set rockspecs.
Am 26.11.2013 19:29 schröbte Reuben Thomas:
> On 26 November 2013 06:00, Philipp Janda wrote:
>> Nah, the multiarch support was more about finding external dependencies
>> in the multiarch library directories than about storing extension
>> modules in arch-specifi
Am 26.11.2013 00:51 schröbte Reuben Thomas:
> Hi,
Hi!
>
> I just upgraded from luarocks 2.1.0 to 2.1.1. I see it supports multiarch
> in some way. I searched a bit and found something about
> external_deps_subdirs and runtime_external_deps_subdirs on the page
> http://luarocks.org/en/Config_file_
Am 18.11.2013 17:33 schröbte Carsten Weise:
> However, on trying to install the first package, xavante, I get the
> following error:
>
> luasocket.c
> src/wsocket.h(15) : error C2061: Syntaxfehler : Bezeichner
> 't_sockaddr_storage'
> src/wsocket.h(15) : error C2059: Syntaxfehler : ';'
>
> so it's
Am 30.10.2013 22:24 schröbte Hisham:
> On 30 October 2013 06:30, wrote:
>
>> The copyright notice is about half-way down that page :
>>Copyright (c) 2007 Olivetti-Engineering SA
>>Permission is hereby granted, free of charge, to any person
>>obtaining a copy of this software and assoc
Hi Hisham,
could you add those rockspecs to the repository, please?
Am 20.10.2013 12:54 schröbte Philipp Janda:
> https://raw.github.com/siffiejoe/lua-modjail/master/modjail-0.1-1.rockspec
> https://raw.github.com/siffiejoe/lua-cprint/master/cprint-0.1-1.rockspec
> http://siffiejoe.
Am 21.10.2013 03:25 schröbte p...@pjb.com.au:
>
> That fixes what I had thought was a bug in readkey. Another version
> of readkey could also happen sometime: my debian wheezy interrupts
> posix.read() even for a SIGWINCH, and returns nil. I fear manually
> restarting interrupted system calls mig
Hi!
modjail:
Another attempt at solving the "unwanted globals" problem. Loads every
Lua module in its own environment with a (lazy) copy of all globals, so
that changes made by one module don't affect the global environments of
other modules or the main chunk.
https://raw.github.com/siffiejoe/l
Am 11.10.2013 22:05 schröbte Hisham:
>>
>> Did you alter the rockspec because it failed to install on your system? Or
>> did you just review and fix it on sight?
>> If the former, then there is a platform difference between Windows and Unix.
>
> The former. Just tried it again here with "lua == 5.
Am 12.10.2013 07:05 schröbte Journeyer J. Joh:
> Hi list,
Hi!
>
> I found a problem in using 'luarocks'.
>
> I cloned luarocks above and 'configure' and 'make build' then 'make install'
>
> ./configure --prefix=/home/hum/rootfs_orbit
> --rocks-tree=/home/hum/rootfs_orbit
> --with-lua-include=/hom
Hi!
Am 02.10.2013 11:52 schröbte John Hind:
> I'm still having trouble getting up and running on luarocks. I'd be grateful
> if an expert could have a look at my repository at:
>
> https://github.com/JohnHind/Lua_Bitfield/
>
> and advise if the rockspec looks OK.
>
> When I try this version on my
Am 26.09.2013 00:30 schröbte p...@pjb.com.au:
> Philipp Janda schröbte:
>> you could modify the `defaults.external_deps_dirs` variable
>> in `luarocks/cfg.lua`
>
> I tried:
> defaults.external_deps_dirs = { "/usr/local", "/usr",
>
Am 25.09.2013 10:42 schröbte p...@pjb.com.au:
> Philipp Janda schröb:
>> The `description.homepage` field is intended to give credit to the
>> upstream module author(s), so you shouldn't change that from its current
>> value. However there is a `description.mai
Am 25.09.2013 06:44 schröbte Philipp Janda:
> Hi!
Hi again!
>
> Am 25.09.2013 05:23 schröbte p...@pjb.com.au:
>>
>> [...]
>
> Here is what you can do:
>
> [...]
I just realized that you already submitted several rockspecs, so this
was probably a lot mo
Hi!
Am 25.09.2013 05:23 schröbte p...@pjb.com.au:
> Hi. On debian stable but with 5.2 in /usr/local/bin, I did:
>luarocks install lgdbm GDBM_LIBDIR=/usr/lib/i386-linux-gnu/
> and it ended up in /usr/local/lib/lua/5.2/gdbm.so
> But, trying to use it reveals:
>undefined symbol: luaL_regist
Am 29.08.2013 01:36 schröbte Hisham:
>
> I think I got it!
>
> https://github.com/keplerproject/luarocks/commit/4744dc4520e9129a8c98b76c63d341e0e66a7ca0
Works for me now. Thanks!
>
> -- Hisham
>
Philipp
--
Learn the l
Am 27.08.2013 18:56 schröbte Hisham:
> On 10 August 2013 06:03, Philipp Janda wrote:
>>
>> Here is my configure incantation:
>> ./configure --prefix=/home/siffiejoe/.self/programs/luarocks-2.1.0
>> --lua-version=5.2 --lua-suffix=5.2
>> --with-lua-includ
Am 10.08.2013 00:16 schröbte Hisham:
> Hi everyone,
Hi!
>
> [...]
>
> * 'make bootstrap' is now an advertised option for installing LuaRocks
> itself as a rock on Unix systems
`make bootstrap` errors out for me:
LUA_PATH="$PWD/src/?.lua;$LUA_PATH" src/bin/luarocks make rockspec
--tree="/h
Am 04.07.2013 12:53 schröbte Philipp Janda:
> That little bug[1] is still not fixed in the git repository ...
> I thought it was overkill in this case, but if you want I can try to
> figure out forks and pull requests on github.
>
> [1]: http://sourceforge.net/mailarchive/mes
Am 03.07.2013 16:24 schröbte Hisham:
> BTW, I just caught a last-minute error in this rc1. To install it
> _not_ as a rock, there's a typo: you need to type 'make built; make
> install'. The next rc will use 'make build; make install'.
That little bug[1] is still not fixed in the git repository ..
Am 19.06.2013 13:14 schröbte Alexey Melnichuk:
> Philipp Janda writes:
>>
>> The preferred way to handle this would be to create a single rockspec
>> that works for both Lua versions.
>
> I can not modify source. I can only write rockspec file.
> Can we detect Lua v
Am 19.06.2013 11:48 schröbte Alexey Melnichuk:
> Hisham hisham.hm> writes:
>>
>> On 17 June 2013 08:33, Alexey Melnichuk wrote:
>>> 1. lbase64
>>
>> I've been using release dates as versions for all lhf modules, so I
>> renamed them to 20120820-1 and 20120807-1, respectively.
>>
> I just try `lua
Am 09.06.2013 17:36 schröbte cyril Romain:
Hi,
Hi!
Here is the rockspec file of lrandom for lua5.2.
It is an update of the existing rockspec but with lua >= 5.2 dependency,
version updated (and md5 of course).
Although the currently available lrandom-20101118-1.src.rock has the
"lua >= 5.1"
Am 07.05.2013 18:05 schröbte Jack Lawson:
> Or you could just fork the code and upload a new version of the rock and
> use and promote that,
New name or old name? If new name, you basically get *more* unmaintained
rocks in the repository (see lposix vs. luaposix). You would also have
to change/f
Am 07.05.2013 10:37 schröbte Thijs Schreijer:
>> -Original Message-
>> From: Philipp Janda [mailto:siffie...@gmx.net]
>> Sent: dinsdag 7 mei 2013 9:59
>> To: luarocks-developers@lists.sourceforge.net
>> Subject: Re: [Luarocks-developers] Hostile rockspec take
Am 07.05.2013 08:44 schröbte Thijs Schreijer:
>>> I do agree that some tighter security controls would be nice on LuaRocks
>>> and its community, but the reality is that it is still a one-man-
>> operation.
>>
>> That's totally true, we can't expect Hisham to scale up indefinitely ;)
>> How to dist
Am 07.05.2013 08:27 schröbte steve donovan:
> On Tue, May 7, 2013 at 7:47 AM, Thijs Schreijer
> wrote:
>
>> - Lots of code still having the 'module' statement
>
> That at least is not a problem, since in practice people use the
> 'compatible' build of 5.2. Which also defines global 'unpack' as wel
Am 07.05.2013 00:46 schröbte p...@pjb.com.au:
> Greetings :-)
Somebody is in a good mood ... :-)
>
> Well, just so the other point of view gets represented...
>
> Philipp Janda wrote:
>> I want to start a discussion, what (if anything) can
>> be done to improve the st
Am 07.05.2013 00:31 schröbte Jack Lawson:
> Allowing any arbitrary person to update another person's rockspec sounds
> very dangerous to me; I could imagine a developer of a popular library
> going afk, and someone else uploading a "lua version change" rockspec that
That would be *a year* of AFK b
Am 07.05.2013 00:01 schröbte Thijs Schreijer:
> Wrt hostile takeover; It has been mentioned before to split the role of
> developer and packager.
The developer is not at fault here, the hostile takeover is with the
packager who incorrectly stated overly optimistic dependencies ...
>
> Thijs
Ph
Hi!
Am 06.05.2013 22:09 schröbte Jack Lawson:
> On Mon, May 6, 2013 at 12:28 PM, Doug Currie wrote:
>
>> no rockspec may be posted on the official repositories unless it specifies
>> a maximum compatible version of Lua.
>
>
> Completely disagree; I think it'd be far better that a majority of olde
Hi everyone!
Lua 5.2 is over a year old by now, and there are still many libraries on
the rocks server that are not yet ported to it. In principle there is
nothing wrong with that, except almost all rockspecs claim compatibility
with Lua 5.1 *and up* ("lua >= 5.1") even if the authors know (and
Hi!
Am 01.05.2013 20:43 schröbte Hisham:
> It didn't? I just tested it here and it seems to pass the flag. Just
> to be clear, this 'defines' table is supposed to be inside each
> module's entry in a builtin-type build section, like this:
>
> build = {
> type = "builtin",
> modules = {
>
Hi!
lbci[1] for Lua 5.2 has been released by lhf. I have made a rockspec and
a matching tarball, that supports Lua 5.1 and Lua 5.2. The rockspec is
attached, the tarball can be found here[2] temporarily, but I kind of
assumed that the tarball would be hosted on the luarocks server like
before
Am 24.04.2013 11:12 schröbte steve donovan:
> On Wed, Apr 24, 2013 at 9:54 AM, Hisham wrote:
>
>> (BTW, this looks pretty interesting, I'll have to take a closer look
>> at it when I get back home!)
>>
>
> I agree, it implements David M's docstring pattern very cleanly:
>
> http://lua-users.org/wi
Hi!
I have another library for the gallery:
As lapp[1] creates a parser for commandline arguments from the usage
message, this module creates type checkers for function arguments and
return values from the function's docstring (or rather from a function
signature therein).
The rockspec is her
Am 19.04.2013 10:51 schröbte steve donovan:
> The current rockspec up in the repo is
>
> http://www.luarocks.org/repositories/rocks/penlight-1.1.0-3.rockspec
>
> and it should be ok, except people on Windows have reported a problem
> because the source contains an extra directory platf which is not
Am 18.04.2013 23:26 schröbte Hisham:
>
> Perhaps this fixes the problem François Perrad was having with his rockspec!
Yes and no. He definitely hits the bug with one of his patches, but
first you need to change
luarocks/tools/patch.lua:298
local match = line:match("^--- ([^\t ]+)")
to
l
Am 18.04.2013 20:15 schröbte Petite Abeille:
>
> On Apr 18, 2013, at 7:53 PM, Hisham wrote:
>
>> PS: "Am 17.04.2013 11:33 schröbte Philipp Janda:"... "schröbte"? What
>> language is this?…
>
> Conjectural evidences would point to German, perhaps a l
Am 17.04.2013 11:33 schröbte Philipp Janda:
>
> luarocks help
>
> gives
>
> Error: LuaRocks 2.0.13 bug (please report at
> luarocks-developers@lists.sourceforge.net).
> ...rams/luarocks-2.0.13/share/lua/5.1/luarocks/help.lua:82: attempt to
> concatenate local '
Am 17.04.2013 03:01 schröbte Hisham:
> Hi everyone,
Hi!
>
> I'm glad to announce LuaRocks 2.0.13. LuaRocks is a package management
> system for Lua modules. (For more information, please visit
> http://luarocks.org )
>
> [...]
>
> As usual, see the GitHub logs for detailed history. And as always,
1 - 100 of 101 matches
Mail list logo
