Hello all,
Again, me and Perry Werneck have been building ooRexx for SUSE and other 
distros on SUSE's Build Service for a while now. It's available from SUSE's 
official repositories.

This is the devel project, for SUSE-based distros and RHEL:

https://build.opensuse.org/package/show/devel:languages:misc/ooRexx

And this is Perry's branch, for other distros (including Fedora, Debian and 
Ubuntu):

https://build.opensuse.org/package/show/home:PerryWerneck:pw3270/ooRexx

We did rewrite the SPECs and added a couple of patches, though. We could work 
something out if someone needs maintainer access to it.





SUSE

Erico Mendonça
Dedicated Support Engineer

(Work)+55 (61) 8594-9557
(Main) +55 (11) 3345-3900

(Personal) +55 (61) 9115-3256


[email protected]





>>> René Jansen <[email protected]> 03/06/15 13:31 >>>
Dan and others,

I am working on this issue. In the meantime, we have a small group building 
ooRexx on their own machines, as an interim solution. I have, unfortunately, 
fallen ill a week ago, but right before that, I have spoken to Mark Hessling 
and Chip Davis about a new build machine, and to the small group of volunteers 
who are building ooRexx ‘at home’.

In the meantime, I still need to receive the KVM code that sets up the VM’s; 
there is no need for the build machine to be in one place though, we might also 
set up a series of machines around the world and coordinate the builds 
centrally, or even just have a scheduled pull & build from crontab. My 
preference however is a Jenkins instance that delivers meaningful feedback to 
the developer that did a checkin and gives us a dashboard to look at the status 
of the platform builds.

At the moment I am most interested to get in touch with people who can provide 
support for less used platforms. What we need to build is a community that can 
support ooRexx on different platforms and can share the burden of work that 
needs to be done; automation is our friend here and needs to be set up quickly.

At the moment, the core building group consists of:

Jean-Louis Faucher: MacOSX Ubuntu Windows 8.1, Publican (Documentation)
Michael Lueck: Ubuntu, Debian
René Jansen: RaspPi(debian) MacOSX z/OS Linux for Z

Dave Jones (Linux for Z)
Enrico Sorichetti (Cmake & Clang (MacOSX, WindowsXP))




In the coming weeks, we will be working on tests for 5.0, and additional 
installers for 4.2.0. At the moment, I am not sure what part of the testsuite 
is cleared by 5.0, and I would like to be able to divide up that work between 
some people over different platforms. I think the building will need to get 
priority after we have cleared that hurdle.

One of the things that the team is going to be working on, is the ‘portable’ 
version of ooRexx, which can be installed from zip archive and will need no 
admin authorities. If done well, this should also cover some X86 Linux 
distributions where we do not have a build. Also, more work needs to go into 
the package managers like yum, apt-get and brew, not to mention docker and 
vagrant images, because those seem the current wave of how people want to get 
their software.

I will be putting up a table of builders on the oorexx website, and I think it 
would be a good idea if we put the names over there of the people who want to 
take first responsibility for a platform (OS, version, instruction set 
architecture. When we have sorted things out, the build machine will follow 
soon.

At the moment we miss Solaris, AIX, Beaglebone, z/VM - who steps up?

best regards,

René.

> On 3 jun. 2015, at 17:15, Dan Carter <[email protected]> wrote:
> 
> Jon, what are the characteristics (bitness, OS, etc.) that are needed?
>  




------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to