Good call for a thread.
First, I am beginning to develop with Corona and this exact issue appeared
in front of me: How to deploy libs loaded by LuaRocks in the final Corona
build (targeting a Android or iOS device).
Second, regarding the documentation.
I always feel hard to understand how to acomplish some simple tasks with LR:
1 - How to install and get it configured (rocktrees, repositories, paths)
2 - How to use LR with multiple Lua versions.
3 - How to upgrade LR
4 - How to deal with differences in configuration between distributions of
LR. For example: LR that comes with LuaForWindows is an old version and the
new versions use different paths for lua libs, scripts and so on.
I think that most of the difficulty I feel comes from the fact that
understanding the concepts of repositories, rock trees, and how to manage
libs and scripts is not very clear. I think it lacks some exemples of how
to get these tasks done.
I would feel very glad if LR project could achieve the same level of
documentation as the GIT project. GIT documentation is awesome. If I have a
doubt it is really fast to find exact what I need and get things done. And
i guess GIT is far more complicated than LR.
I began to write my own notes to guide myself but as I need to deliver my
projects its not easy to keep the pace in this task.
So, I hope that these impressions are helpful.
I'd really appreciate if nobody comes with the "This is open source. You
can do it yourself" or "Where is your contribution" argument. While I do
think that LR is a very nice project, I see myself as a user of the project
and I'm giving feedback based on my experience hoping it will be some
useful for the project.
So, in short. LR documentation should be able to easily allow one to create
a mental model of how LR works, just how GIT achieves this goal.
Best regards
Eric Chiesse
2016-01-28 23:03 GMT-02:00 Hisham <h...@hisham.hm>:
> On 28 January 2016 at 18:05, leaf corcoran <lea...@gmail.com> wrote:
> > Hello list,
> >
> > I've been talking to a few people about what needs to be done encourage
> use
> > of LuaRocks in more places within the Lua community. A common request is
> "I
> > wish LuaRocks installed packages in the current directory like npm." It
> bums
> > me out to hear that because it's definitely already possible, but
> > non-explicit documentation hides the feature.
> >
> > I wrote a guide explaining about how LuaRocks installs packages, and how
> you
> > can use it to install packages to the local directory:
> >
> > http://leafo.net/guides/customizing-the-luarocks-tree.html
>
> This is excellent for two reasons: one, for directing people on how to
> get things done, and two, for allowing us to take a look at it and
> criticize the current process. What could we change in LuaRocks to
> make this use-case simpler?
>
> -- Hisham
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Luarocks-developers mailing list
> Luarocks-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/luarocks-developers
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
