> Am 28.10.2021 um 21:15 schrieb CVBruce <cvbr...@gmail.com>:
> 
> Well, I don’t think this will be popular, but I think that a lot of these 
> problems are caused by treating ooRexx as an application.
> 
> To me ooRexx is a tool used to create applications, like clang, or python.
> 

I do not think anyone disagrees :-)

> I use the MacPorts package manager, and have tried Brew and fink package 
> managers, and they never have a problem with all of the security issues that 
> you mention. Or if they do, they seem to work them out so that they are 
> transparent to me. All three package managers install to their own areas of 
> the directory that don’t seem to interfere with Apple’s security.

The current DMG „installer“ is sudo-free and install to any place the user 
desires to put it in. All that is needed is to modify the path to include the 
/bin directory of ooRexx.
 
That said it would indeed be desirable to create packages for Homebrew, 
MacPorts and any other packet handling system, It would be great if you have 
connections and can reach out to them and ask what they need. The installation 
package for ooRexx is universally relocatable and would be easy to put in at 
least a „bottle“ for Homebrew. The current DMG is nothing more than a zipped 
copy of the files built and could be mounted and dragged along to any place on 
the machine.

> 
> Upgrades from one MacOS level to the next do require some work, but  work 
> that I would be doing anyway for all the other tools that I use, for example 
> to build ooRexx from source.

This upgrade problems are not to be ignored. On Catalina Homebrew was in 
/usr/local per default whereas in Big Sur is appears to be in /opt? When 
upgrading a Catalina machine to Big Sur I found myself with a non-standard 
setup. Apple are notorious in moving things around. The move from /usr to 
/usr/local for user defined installations some versions ago is what broke the 
(still only) Official ooRexx 4.1.2 installer for instance.
> 
> Rather than a .DMG file that you can download and run the mac installer, I’d 
> rather have something that the MacPorts package manager can download and 
> install.
> 

I don’t see why we can´t have both?

> Anyway that’s my 2¢
> 
> Bruce
> 
>> On Oct 28, 2021, at 7:25 AM, Rony G. Flatscher <rony.flatsc...@wu.ac.at> 
>> wrote:
>> 
>> Just got an upgrade option from BigSur 11.6 to Monterey 12.01.
>> 
>> It seems that with each upgrade of macOS there are new "security" related 
>> crash walls erected (some
>> things that used to work all of a sudden do not work anymore as before). 
>> Short of time wondering
>> whether it is seen to be important to upgrade to Monterey now or whether it 
>> would be o.k. to wait a
>> few months until enough new Apple users with that macOS enter the scene. 
>> What do the Apple users in
>> this list think?
>> 
>> ---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



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

Reply via email to