On 28 May 2014 15:41, Sebastian Moreno <smoreno...@gmail.com> wrote:
> Hisham,
>
> There is a way to specify dependencies versions and custom rocks servers?
Dependency versions: yes, in the dependencies table.
Custom rocks servers: yes, through the --server flag.
In the previous example, it would be something like this:
$ cd
$ mkdir isolated
$ cd isolated
$ echo 'package="myenv"; version="1.0-1"; source={url=".";dir="."};
dependencies={"luasocket", "ansicolors > 1.0"}; build={type="none"}' >
myenv-1.0-1.rockspec
$ luarocks install ./myenv-1.0-1.rockspec --tree=$PWD --deps-mode=one
--server=http://rocks.moonscript.org
You can't say "fetch this rock from this server and that rock from
that server" but I don't think that's a good feature to have.
Encouraging rockspecs with explicit URLs in the dependencies section
would defeat mirroring of repositories.
> That was my problem at the time I was writing Moonbox (at least one of
> them), I din't have a way to distribute which rocks versions (with custom
> servers sometimes) my app needed to run properly.
If one needs a specific set of rocks coming from different places, an
option is to host their own rocks server (i.e., upload the set of
rocks plus a manifest file to a web-accessible directory such as a
Github repo).
Having said that, nice frontend tools to manage all this LuaRocks
plumbing and setup a nice environment for the user are certainly a
cool thing. I haven't used Vert or Moonbox myself, but if you guys
felt the need to write them, I'm sure the use-case is there.
-- Hisham
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
