Hi P.O.,

great! no problems here, if you put the script somewhere I can test it, I will 
add it to the build machine. I will try to test the T20 as soon as I can. 
Having some connectivity problems today but maybe tomorrow.

best regards,

René.

> On 15 Nov 2018, at 18:02, P.O. Jonsson <oor...@jonases.se> wrote:
> 
> Dear René,
> 
> In principle I have (almost) all the steps ready to do a .dmg installer, with 
> some limitations. I did not manage to get it all controlled from CMake but 
> would an afterburner shell script be so bad?
> 
> CMake <complex command>
> make
> make install
> bash afterburner.sh 
> 
> There are ways around sudo password
> 
> https://discussions.apple.com/thread/4469969 
> <https://discussions.apple.com/thread/4469969>
> 
> And I would expect that on a machine with a strong password for remote login 
> (my ooRexx Mac mini) used by a single user (Jenkins) for the sole purpose of 
> building ooRexx such use would be acceptable, security wise, or do you 
> disagree?
> 
> Using this method it is possible to create the entire chain of commands set 
> out above without any user interaction. I have tried it out on my own machine 
> and it does work (but is a bad idea for permanent use on a „normal“ user 
> account, I know).
> 
> Personally I have nothing against two or more „official" ooRexx installers, 
> one for /opt, one for ~/Applications and the BSF4ooRexx installer (but that 
> might suffice to link to). For the two first I think I can do a dmg installer 
> but bear with me for a week or so, I am quite busy with non-oo stuff and I 
> also want to finalize the test cases for the sample files (and test them).
> 
> Regarding Jenkins Master I have offered the T20 Windows machine as a host 
> (test is up&running at http://jonases24.asuscomm.com:50000/login?from=%2F 
> <http://jonases24.asuscomm.com:50000/login?from=/>) but on second thoughts I 
> think it might be bad idea to have the Jenkins Master on a physical machine 
> needing maintenance and support. I have virtually no knowledge on how to 
> manage the environment where Jenkins is currently running and I think a 
> rented server/cloud solution would be a safer and more stable situation. The 
> T20 could then be used to host the slave for Windows 10 32/64 or whatever is 
> needed. But if you find time to do a test please give it a try, the machine 
> is not used for anything else.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se <mailto:oor...@jonases.se>
> 
> 
> 
>> Am 15.11.2018 um 17:17 schrieb René Jansen <rvjan...@xs4all.nl 
>> <mailto:rvjan...@xs4all.nl>>:
>> 
>> I agree, but as said before, I think it was Rick, we need an automated Mac 
>> installer that is integrated into the CMake build lists.
>> 
>> One way to accomplish that is to move forward the no-admin version, we could 
>> then just automate building a .dmg with the materials on it, to move to a 
>> suitable location - ~/Applications comes to mind. When there is knowledge of 
>> scriptable installer builders, we need to use that. Since I made the first 
>> Mac installers with the awkward dialogs and scripts a lot has changed. I 
>> will communicate with P.O. and Enrico and see what can be done.
>> 
>> I still need to move the Jenkins to a place where it keeps working and then 
>> we can release from there and upload to SF. I will try to put together a 
>> checklist on the wiki on SF (it has one doesn’t it). When we have worked on 
>> that, we’ll need to confer with Erich and Rick, and branch.
>> 
>> 
>> best regards,
>> 
>> René.
>> 
>> 
>>> On 15 Nov 2018, at 10:17, Rony G. Flatscher <rony.flatsc...@wu.ac.at 
>>> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>>> 
>>> This past year there have been many remarkable changes (performance 
>>> improvements from 1.2x to 20x
>>> times, memory management, multi threading) and additions (ADDRESS...WITH, 
>>> variable references) to
>>> ooRexx 5.0 beta, which already was great with respect to valuabel and new 
>>> features a year ago!
>>> 
>>> Judging from my work on BSF4ooRexx and ooRexx projects, ooRexx 5.0beta has 
>>> become stabler, faster
>>> and more versatile than the almost five years old ooRexx 4.2.0 (release 
>>> date: February 2014).
>>> 
>>> Therefore, I think, it is time to create a release version of ooRexx 
>>> 5.0beta, such that companies
>>> and organisations become able to install and take advantage of it! (As long 
>>> as software is dubbed
>>> "beta" it usually does not get deployed for professional purposes in 
>>> organisations.)
>>> 
>>> So I suggest to create a branch 5.0.0 which does not take any new features 
>>> anymore, just bug-fixes
>>> and materials to complete it (e.g. test units, documentation) "as fast as 
>>> possible". (Any new
>>> features would go to trunk only and could be used to create a 5.1 version 
>>> shortly after the release
>>> of 5.0.)
>>> 
>>> ---rony
>>> 
>>> P.S.: After the release of 5.0 I would really suggest to create a version 
>>> 5.1 as soon as possible
>>> thereafter, which allows ooRexx to be run without administrative privileges 
>>> on Windows, Linux and
>>> MacOSX!
>>> 
>>> P.P.S.: There are many important additional features for ooRexx post 5.x 
>>> like Unicode-support, now
>>> that even English versions of Windows create Unicode text files by default, 
>>> let alone international
>>> users of ooRexx with a need for support for their culture's glyphs (also 
>>> speeding up/simplifying
>>> interfacing with Unicode-systems like Java, applications employing Unicode 
>>> for which ooRexx should
>>> serve as a scripting language, but also operating systems like Linux, 
>>> MacOSX and Windows). Or
>>> getting a NetRexx like catch-finally construct, or ... much, much more! :)
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net 
>>> <mailto:Oorexx-devel@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> 
>> 
>> 
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> <mailto: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

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to