No problem with me. What I would *most* like is that we can build the package in Jenkins and it will be automatically obviated by new builds.
René. > On 30 Sep 2020, at 15:43, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote: > > Tomorrow there will be a presentation entitled "Running Rexx from a USB > drive" at this year's > International Rexx symposium (cf. > https://www.rexxla.org/events/2020/schedule.html). In the meantime > I finalized the USB-package and it it should be ready for testing and will > demonstrate it tomorrow > at the symposium. > > Now, it would probably make sense to make it also available to interested > parties for evaluation and > testing as it includes ooRexx 5.0 r12113 for MacOS (Darwin), Linux (32- and > 64-bit) and Windows (32- > and 64-bit). > > So now I am contemplating to make it available in the sandbox directory of > the ooRexx project for > others to get access to the package. The zip-archive is appr. 40MB and comes > with a short readme.txt > file. > > The question for the developers: is that o.k. with you? An alternative would > be to use a different > location instead. > > It would be important to remove that particular package ASAP as new versions > of ooRexx in the trunk > should obsolete this particular package, such that ooRexx programmers do not > get outdated software > after a while. OTOH it allows you to check it out and contemplate whether we > should also create > "stick"-versions of ooRexx for all the supported platforms. > > ---rony > > > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
