Well, it can only be on the supported list if someone builds and provides a package that can be downloaded. Since we do not yet have such a package for MacOSX for the 4.0 beta, it would currently need to be described as "unsupported". We don't have a package, and you've not shown any signs that you intend to continue building it, so I don't see that we can make any other statement at this point.
Additionally, will you have build this in the past, you've never contributed back any notes on what's required to build the MacOSX deliverable, details on the install and packaging etc., so that others can build the interpreter independently. The type of information that Rainer has contributed for AIX is a good model for the type of information. An open source community is a community of volunteers. There are no "job assignments" like a commercial software projbect. Since you never responded to any of the discussions about building a MacOSX version for the beta, the reaonsable interpretation was you'd lost interest in being involved with ooRexx. That happens all the time with open source software projects. When it happens, you continue on supporting the things with the resources/expertise you have available. That statement was not meant to be directed at you, but was rather a statement of the situation as it exists today. We have no MacOSX version for the beta because we have not means to build one. We'd like to have one, but it will require someone to step up and do some work for that to happen. Rick On Sun, Apr 19, 2009 at 9:45 AM, René Jansen <rvjan...@xs4all.nl> wrote: > Allow me to express a small bit of surprise here. I have debugged, > tested and packaged every major and minor release of ooRexx for MacOSX > since 2006. I have always answered every email about installing ooRexx > on the Apple Mac and supported issues with it numerous times. Every > release of ooRexx for MacOSX for every available instruction set > architecture on the Mac has a binary installer on SourceForge, > provided by me - including integrated and tested BSF4Rexx. > > There is no reason yet to assume this release will be different. So I > am at least a bit worried about seeing the "none of the committers" > and "not on the supported list" parts again. > > MacOSX is a supported platform from the beginning, and on the > supported list already for a long time - see the website. Actually, > MacOSX is one of the reasons contributing to open sourcing of the > interpreter product. So am I ignored here on purpose, or are there > other things going on? The thing about building a community - well you > have to build a community. I am not going to ask to be asked becoming > a committer - but it might even have saved us redoing some patches. > > So please inform me why this has to be like this. > > best regards, > > René Jansen. > > On 18 apr 2009, at 19:36, Rick McGuire wrote: > >> Klaas, >> >> The code is not going to get any more mature than it is at this point. >> It should be hardward agnostic, so the architecture of your machine >> should not be a problem. The only reason it has not been made >> available on the Mac yet is because of a lack of someone to do the >> actual port. We're willing to give you assistance on doing this, but >> there are a few things you need to understand: >> >> 1) None of the committers have access to the combination of >> hardware/software that you do, so you'll have to be willing to get >> your hands dirty and try to debug things if there are problems. The >> more information you're able to provide on any issues, the more likely >> we'll be able to help you. >> >> 2) We're not likely to be able to provide much asistance on compile, >> build, or install issues. None of us are Mac experts, so you're >> probably going to need to research those sorts of issues yourself. >> >> 3) Once you do the port, you might be called upon to help any users >> that have issues on that platorm. >> >> As long as you keep these points in mind, we'd love to add more >> platforms to our supported list. >> >> Rick >> >> On Sat, Apr 18, 2009 at 1:23 PM, Klaas. <kpli...@xs4all.nl> wrote: >>> Hello, >>> After following the test efforts up to now >>> with admiration for you guys, I thought I'd >>> join in and get some testing done. >>> My test hardware is a PowerMac G5, with >>> OS X 10.5 and openSuse 11.1, both have >>> ooRexx 3.2 installed. >>> However after an hour or so at this task, >>> I am wondering if this is opportune. Mac OS X >>> is mentioned nowhere, Linux is, but openSuse? >>> There is a package .bff (?) for Power 64. The >>> CPU in the PowerMac is an IBM 970, which runs >>> 64 bit but I don't know if it is supported. >>> >>> In short : should I spend time on getting this >>> to run?, which means I will have to get some >>> support from the experts in this list. >>> >>> My goal for testing: >>> - response to the request for testing so that I >>> feel a little less "quilty" using this product >>> - try to convert my "PyRex" (Rexx+Python) code >>> for a socket processing program to the new >>> ooRexx 4 code. >>> >>> Mission impossible? Or just wait until the project >>> is more mature? >>> >>> greetings, >>> Klaas Punt >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Stay on top of everything new and different, both inside and >>> around Java (TM) technology - register by April 22, and save >>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >>> 300 plus technical and hands-on sessions. Register today. >>> Use priority code J9JMT32. http://p.sf.net/sfu/p >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >> >> ------------------------------------------------------------------------------ >> Stay on top of everything new and different, both inside and >> around Java (TM) technology - register by April 22, and save >> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >> 300 plus technical and hands-on sessions. Register today. >> Use priority code J9JMT32. http://p.sf.net/sfu/p >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
