Status report on the CI server.

[Peter Drahoš]

I have recently finished the setup of the CI server VMs that will be
used to evaluate LuaDist/LuaRocks packages. The process required some
changes to the bootstrap process as well as srlua so the generated
binaries behave correctly on all tested systems. LuaDist now installs
and runs correctly on FreeBSD and Solaris and is periodically tested
against Windows, Linux and OSX targets as well.

Currently only Lua and Bootstrap is tested but after some minor
changes that need to be done to luadist-git I will add all packages
from LuaDist repository to the CI.

The next step is to implement the manifest generator that will open
some new possibilities for the luadist-git tool as well as provide
needed information for other related projects such as intellua.

pd

[steve donovan]

On Wed, Apr 10, 2013 at 11:48 AM, Peter Drahoš <dra...@gmail.com> wrote:

The next step is to implement the manifest generator that will open
some new possibilities for the luadist-git tool as well as provide
needed information for other related projects such as intellua.

That is going to be a big step forward!  Thanks, Peter and Andrew.

Then I can work on the graphical installer and have an authoritative manifest to work with.

Generally this is excellent news, I think it's the first time an open-source Lua project reached this level of technological maturity.

[Andrew Starks]

On Thursday, April 11, 2013, steve donovan wrote:

On Wed, Apr 10, 2013 at 11:48 AM, Peter Drahoš <dra...@gmail.com> wrote:

The next step is to implement the manifest generator that will open
some new possibilities for the luadist-git tool as well as provide
needed information for other related projects such as intellua.

That is going to be a big step forward!  Thanks, Peter and Andrew.

I echo the sentiment, except for this part. It has been 100 percent Peter's hard work. The progress has been quite literally due to his labor,

Thank you, Peter!

-Andrew 

[Andrew Starks]

Again, this is great work, and thank you!

I was contemplating the use of this for a project at work. I got hung up on trying to deploy it on windows with Lua 5.2. It said, in effect, that there was a conflict with the installed 5.1.x and I couldn't get bootstrap to run with 5.2. In the limited time that I had, I also couldn't figure out how to get the thing to spawn an alternate tree with 5.2 and required dists. 

Is that where things are at or did I just mess something up?

[Peter Drahoš]

On 11 Apr, 2013, at 11:27 , Andrew Starks <andrew...@trms.com> wrote:

> I was contemplating the use of this for a project at work. I got hung up on trying to deploy it on windows with Lua 5.2. It said, in effect, that there was a conflict with the installed 5.1.x and I couldn't get bootstrap to run with 5.2. In the limited time that I had, I also couldn't figure out how to get the thing to spawn an alternate tree with 5.2 and required dists.

The luadist-git CLI app is bound to lua-5.1.5 by luasocket which has not yet been updated to support Lua 5.2. Therefore the default deployment directory LuaDist uses contains lua-5.1.5 which ends up in conflict with lua-5.2. You can however use luadist to install to a different (empty) deployment directory that will pull in the latest lua it can for the given packages you want to install.

Typically:
# By default LuaDist uses deployment directory LuaDist is in
> luadist list
# Lists installed modules, contains lua-5.1.5

> luadist install lua-5.2.2
# Conflict with installed lua-5.1.5

Solution, specify a destination:

# use ~/my_lua as the target installation destination which should be empty
> luadist ~/my_lua list
# Nothing is installed, empty listing

> luadist ~/my_lua install lua-5.2.2
# Install should succeed

> Is that where things are at or did I just mess something up?

You did not. LuaDist prevented you from replacing the lua-5.1.5 which it relies on to lua-5.2.2 which would render it unusable.

There are two solutions to this .. the above approach allows you to install to different destinations whatever you want. The second solution is to update luasocket and luadist-git to support lua-5.2. The later is planned after batteries for lua 5.1.5 have been released.

pd

[Andrew Starks]

Excellent. I'll give it a shot, later. 

Thanks Peter!