Dear Rony, just some thoughts. I did not run the script (yet) but is the intention to create symlinks to /usr/local so as to avoid the need to modify the path?
If the 2nd part is creating the steps necessary to „unlink" why do you not create a shell script of those lines? After all the user will not realize at the time of installation (linking) that he might need them (much) later during an uninstall? (unlinking). It would appear possible to create a static unlink script for the default (/Applications/ooRexx5/bin,lib <-> /usr/local/bin,lib Can we hear from the developers what the skipped files ( callrexx1, callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and oorexx-config.) are for? Can they be safely removed from the installation on macOS? How does one go about it? It is possible to delete these files from the (auto-generated) script building the dmg in a post-process but that would be the ugly way. IMO we should locate the places in CMakelists.txt where those files are copied and fix the problem there. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > Those who use ooRexx5 from Sourceforge on a Mac and who have followed the > instructions will have > ooRexx in "/Applications/ooRexx5". > > The enclosed Rexx script will create the link and remove commands that will > make ooRexx5 available > systemwide. Run it and copy & paste the output to create the links or remove > them. > > If you have ooRexx5 installed somewhere else, adjust the script accordingly. > > ---rony > > > <linkooRexx5.rex>_______________________________________________ > 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
