[Oorexx-devel] ooRexx doc and builds

[René J. <rvj...@xs...>]

The good news is, I can build the ooRexx documentation now in an automated way with Jenkins (with help from Jean-Louis, altough I decided to build on Linux in the end because of too much hassle on MacOSX - but I needed all his tips anyway). So somewhere this weekend we will have nightly builds of the docs on the website.

My first (1) question is, do we have a higher resolution image of the ooRexx logo? This one is not print resolution (it is not even screen resolution and has artifacts) and it needs to be replaced. Also (2), we need a keep-together on the word “documentation" because it is being split on the title pages.

It would be good (3) if someone could work on the makefile to not start with removing the products and only rebuild what is needed, on a publication-base. This way I can parallelize the builds over several machines, we have enough linux nodes for the moment to do that.

I have had several offers of owners of windows machines, and this build is being worked on. More (4) offers for windows are still welcome, though.

For the immediate future I would like to focus (5) on the portable version. My thoughts here are a zip or tar.gz file, with minimal script support for installing the rxapi task. I am optimistic and will assume that if we do not use queues or other ipc, we can use the interpreter to have one installer (6) that switches on OS and does what is needed. The rxapi service (7) needs to run on a high port not to be sudoed or ran with admin rights, and it cannot log its pid file to /var/* but it needs to find some place in the user’s home directory. On MacOSX (8) there is still a problem with the rxapi service task that is being shot down every ten seconds. I have the feeling that these problems once were close to being solved, but I welcome suggestions. Sorry for numbering these propositions but I thought it would come in handy in partial responses.

Are these things people can pick up? I am going to automate running the tests on the platforms next, and then we should have a look at the issues list; when things get moving we should standardize on entering and picking up issues by assigning them to yourself or others, but in this phase I think it is important to pick up some momentum.

best regards,

René.