On Mon, Apr 25, 2011 at 06:40:52AM +0400, Alexander Gladysh wrote: > If you want public attention to your library (a good thing usually — > public does find bugs), announcing on Lua ML is a good idea.
This version was actually released a few years ago (in April 2009 according to luaforge) but I believe I didn't announce it on the ML. I just finally packaged it up for luarocks yesterday. > > [OT: Since the main luarocks server seems to be down (along with the whole > > kepler project site), > > It works from here. > > http://www.luarocks.org/repositories/rocks/ > > The website itself returns 503 though. Thanks, I thought the whole webserver was down. > > maybe a mirror wouldn't be bad? If required, I can host > > one. I assume it's not a huge amount of data anyway?] > > I suggest hosting a mirror on github. > > As I wrote earlier, this construct works: > > $ sudo luarocks install asklua > --only-from=https://github.com/agladysh/luarocks-mirror/raw/master/luarocks.org/repositories/rocks/ > Installing > https://github.com/agladysh/luarocks-mirror/raw/master/luarocks.org/repositories/ > > Hisham, is there a way we could setup such a mirror so it would be > updated when main repo is updated and it is not burdens you to > maintain it? I think that this would be good for the LuaRocks project. In case you end up doing it with git: maybe a post-commit hook? > (The most straightforward way is to put all this stuff under Git and > do commit and push each time — but I assume this is not comfortable > for you.) Yes, that would indeed be one convenient way to do it. The other one would be running rsyncd and feeding mirrors through that. If you don't throw old rockspecs away, putting it under version control does not make much sense, although it might preserve accidental deletion etc. Hisham, thanks for adding it! Best regards, Moritz _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
