it is great if it works but it is def old skool. This is the type of work (evaluating code against releases of whatever) that anyone I work with (yes, very young people, well compared to us) would do in a docker container. I am a bit worried about the release schedule (what release schedule?) but I am ok with either fixing or postponing it, not really with spending a lot of time on it.
With the documentation going well we should try to avoid breaking change and focus on showstoppers IMHO. René. > On 7 Apr 2020, at 13:11, Rony <rony.flatsc...@wu.ac.at> wrote: > > It may be true that one can individually change the ooRexx location and > version by changing PATH such that the operating system can find the desired > ooRexx in that particular session that changed the PATH to point to a > different ooRexx.. (This ability will not be lost if supporting > update-atlernatives on Linux, rather new possibilities of installation > combinations that do not break alternate installations becomes possible on > Linux.) > > However, this is not matching what update-alternatives defines and allows for: _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
