Ok Alexander, I'll change to lnotify as soon as possible! Cheers! On Mon, Dec 13, 2010 at 2:19 PM, < [email protected]> wrote:
> Send Luarocks-developers mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers > > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Luarocks-developers digest..." > > > Today's Topics: > > 1. Re: update the package (Gabriel Duarte) > 2. Re: update the package (Alexander Gladysh) > 3. LuaRocks for packaging (1): /../rocks/manifest (Ildar Mulyukov) > 4. Re: [ANN] LuaRocks 2.0.4-rc2 (Alexander Gladysh) > 5. List of files in a rockspec (Alexander Gladysh) > 6. How to stop LuaRocks to mess with my executables? > (Alexander Gladysh) > 7. Re: How to stop LuaRocks to mess with my executables? > (Alexander Gladysh) > 8. Re: Re: How to stop LuaRocks to mess with my executables? > (steve donovan) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Dec 2010 18:11:12 -0200 > From: Gabriel Duarte <[email protected]> > Subject: [Luarocks-developers] Re: update the package > To: luarocks-developers <[email protected]> > Message-ID: > > <[email protected]<aanlktimz66tkmt5jyw54ro%[email protected]> > > > Content-Type: text/plain; charset="utf-8" > > Hello guys, > so, I'm the developer of luanotify, the bind of libnotify to Lua and I was > looking around and I saw another package called luanotify, I was figuring > out that some mistakes could happen because of the similar name of the > packages, then, I decided to to change the name to lua-notify. It's not a > big change, but, at least, is not the same anymore. I'm asking to the > LuaRocks administrators to remove all rockspec and rock files and the > references of the old name. Following the changes, I've updated the code a > little bit and I'm sending the new respectives .rock and .rockspec files. > > I'd be glad to see the changes happen! > > Cheers! > > > On Thu, Dec 9, 2010 at 6:06 PM, Gabriel Duarte <[email protected]> > wrote: > > > Hello guys, > > so, I'm the developer of luanotify, the bind of libnotify to Lua and I > was > > looking around and I saw another package called luanotify, I was figuring > > out that some mistakes could happen because of the similar name of the > > packages, then, I decided to to change the name to lua-notify. It's not a > > big change, but, at least, is not the same anymore. I'm asking to the > > LuaRocks administrators to remove all rockspec and rock files and the > > references of the old name. Following the changes, I've updated the code > a > > little bit and I'm sending the new respectives .rock and .rockspec files. > > > > I'd be glad to see the changes happen! > > > > Cheers! > > > > > > > > -- > > Gabriel Duarte > > Linux User #471185 > > Rio de Janeiro - RJ > > http://w3.impa.br/~gabrield > > > > Phones: > > (55) (21) 9463-7760 -> Mobile > > (55) (21) 2464-9302 -> Home > > (55) (21) 2529-5080 -> Work > > > > > > -- > Gabriel Duarte > Linux User #471185 > Rio de Janeiro - RJ > http://w3.impa.br/~gabrield > > Phones: > (55) (21) 9463-7760 -> Mobile > (55) (21) 2464-9302 -> Home > (55) (21) 2529-5080 -> Work > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.luaforge.net/pipermail/luarocks-developers/attachments/20101209/8b9a7f07/attachment-0001.htm > > ------------------------------ > > Message: 2 > Date: Fri, 10 Dec 2010 06:20:51 +0300 > From: Alexander Gladysh <[email protected]> > Subject: Re: [Luarocks-developers] update the package > To: LuaRocks developers list <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Thu, Dec 9, 2010 at 23:06, Gabriel Duarte <[email protected]> wrote: > > Hello guys, > > so, I'm the developer of luanotify, the bind of libnotify to Lua and I > was > > looking around and I saw another package called luanotify, I was figuring > > out that some mistakes could happen because of the similar name of the > > packages, then, I decided to to change the name to lua-notify. It's not a > > big change, but, at least, is not the same anymore. I'm asking to the > > LuaRocks administrators to remove all rockspec and rock files and the > > references of the old name. Following the changes, I've updated the code > a > > little bit and I'm sending the new respectives .rock and .rockspec files. > > I'd be glad to see the changes happen! > > IMHO, this will not help much to reduce confusion. > > Perhaps you can pick more different name? (Even lnotify would be better.) > > (Note that I'm not a LR maintainer, just a voice from the crowd.) > > Alexander. > > > > ------------------------------ > > Message: 3 > Date: Sat, 11 Dec 2010 01:17:13 +0600 > From: Ildar Mulyukov <[email protected]> > Subject: [Luarocks-developers] LuaRocks for packaging (1): > /../rocks/manifest > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed > > Hello, people. > 1st, I'd like to recognize LuaRocks as most accurate program in Lua > I've seen. It is a good example for me. > I have an idea to use LR for packaging just like jpackage is used for > Java modules. > > The first question I want to ask: > /usr/lib/luarocks/rocks/manifest looks like a cache. How do I restore > it if it's lost? > > The reason behind this question is: if I pack a rock into a native > package format (rpm or deb), this looks like the only file I can't > directly handle. > > Thanks and regards! > -- > Ildar Mulyukov, free SW designer/programmer > ================================================ > email: [email protected] > home: http://johan-notes.blogspot.com/ > ALT Linux Sisyphus > ================================================ > > > ------------------------------ > > Message: 4 > Date: Sun, 12 Dec 2010 13:12:56 +0300 > From: Alexander Gladysh <[email protected]> > Subject: Re: [Luarocks-developers] [ANN] LuaRocks 2.0.4-rc2 > To: LuaRocks developers list <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Nov 24, 2010 at 03:39, Hisham <[email protected]> wrote: > > > Here's a preview release of LuaRocks 2.0.4. This is a release > > candidate: if no problems are reported, these packages will be renamed > > into the final versions. > > Hisham, I'm sorry to nag, but is there a schedule for 2.0.4 release? > > Thanks, > Alexander. > > > > ------------------------------ > > Message: 5 > Date: Mon, 13 Dec 2010 05:03:06 +0300 > From: Alexander Gladysh <[email protected]> > Subject: [Luarocks-developers] List of files in a rockspec > To: LuaRocks developers list <[email protected]> > Message-ID: > > <[email protected]<g33u%[email protected]> > > > Content-Type: text/plain; charset=UTF-8 > > Hi, list! > > I've got a set of lua-only rockspecs which use build "none" or > "builtin" with mix of copy_directories and install.bin clauses. (Maybe > something else, but only build modes are none and builtin only.) > > To determine if I should rebuild a rock, I need a quick and dirty way > to get a list of files which would get into rock file if I'd say > `luarocks make` on that rockspec. > > Note that the list should come with resolved symlinks. > > Any clues? Can I reuse LuaRocks code for that somehow? > > Thanks, > Alexander. > > > > ------------------------------ > > Message: 6 > Date: Mon, 13 Dec 2010 19:08:05 +0300 > From: Alexander Gladysh <[email protected]> > Subject: [Luarocks-developers] How to stop LuaRocks to mess with my > executables? > To: LuaRocks developers list <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Hi, list! > > I've got a small executable Lua script (replaced by silly example below) > > --- filename: bin/foobar > #! /usr/bin/env luajit2 > > print("run under luajit", not not jit) > --- > > I install it with a rockspec: > > build = { > type = "none", > install = { > bin = { > "bin/foobar" > } > } > } > > But when I run it, it reports that it does not run under LuaJIT! > > After a hour of debugging, I've found this: > > --- > $ cat `which pk-call-lua-module` > #!/bin/sh > > > LUA_PATH="/usr/local/share/lua/5.1//?.lua;/usr/local/share/lua/5.1//?/init.lua;/home/agladysh/.luarocks/share/lua/5.1//?.lua;/home/agladysh/.luarocks/share/lua/5.1//?/init.lua;/usr/local/share/lua/5.1//?.lua;/usr/local/share/lua/5.1//?/init.lua;/usr/local/share/lua/5.1//?.lua;/usr/local/share/lua/5.1//?/init.lua;./?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/usr/local/lib/lua/5.1/?.lua;/usr/local/lib/lua/5.1/?/init.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua;$LUA_PATH" > > LUA_CPATH="/usr/local/lib/lua/5.1//?.so;/home/agladysh/.luarocks/lib/lua/5.1//?.so;./?.so;/usr/local/lib/lua/5.1/?.so;/usr/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so;$LUA_CPATH" > export LUA_PATH LUA_CPATH > exec "/usr/bin/lua" -lluarocks.loader > "/usr/local/lib/luarocks/rocks/foobar.module/scm-1/bin/foobar" "$@" > --- > > WTF? > > If my script is a shell-script, then it is copied verbatim, but if it > is a Lua script, it is silently replaced by this monstrocity. > > Why? And how to turn it off? > > Alexander. > > > > ------------------------------ > > Message: 7 > Date: Mon, 13 Dec 2010 19:12:39 +0300 > From: Alexander Gladysh <[email protected]> > Subject: [Luarocks-developers] Re: How to stop LuaRocks to mess with > my executables? > To: LuaRocks developers list <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Dec 13, 2010 at 19:08, Alexander Gladysh <[email protected]> > wrote: > > > build = { > > type = "none", > > install = { > > bin = { > > "bin/foobar" > > } > > } > > } > > > If my script is a shell-script, then it is copied verbatim, but if it > > is a Lua script, it is silently replaced by this monstrocity. > > I could understand this if I used build.type = "builtin" (and even > then I'd like this to be off by default). > > But build.type = "none" must not change any files by definition! > > Alexander. > > > > ------------------------------ > > Message: 8 > Date: Mon, 13 Dec 2010 18:18:57 +0200 > From: steve donovan <[email protected]> > Subject: Re: [Luarocks-developers] Re: How to stop LuaRocks to mess > with my executables? > To: LuaRocks developers list <[email protected]> > Message-ID: > > <[email protected]<ytdbnbsaxhfyds%[email protected]> > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Dec 13, 2010 at 6:12 PM, Alexander Gladysh <[email protected]> > wrote: > > I could understand this if I used build.type = "builtin" (and even > > then I'd like this to be off by default). > > > > But build.type = "none" must not change any files by definition! > > Alas, some operating systems have feeble shells and need the wrapping. > > But certainly in this case one would like some guarantee of sane delivery! > > Maybe something to consider when thinking about the new rockspec format? > > steve d. > > > > ------------------------------ > > _______________________________________________ > Luarocks-developers mailing list > [email protected] > http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers > > > End of Luarocks-developers Digest, Vol 46, Issue 6 > ************************************************** > -- Gabriel Duarte Linux User #471185 Rio de Janeiro - RJ http://w3.impa.br/~gabrield Phones: (55) (21) 9463-7760 -> Mobile (55) (21) 2464-9302 -> Home (55) (21) 2529-5080 -> Work
_______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
