Dear Rony, > >> and and likewise change /share/ooRexx/native.api to >> /share/ooRexx/samples/native.api > > No this currently got changed from "share/ooRexx/native.api" to > "share/ooRexx/samples/native.api“.
Ok I can see this now, the last time I did not get the changes from SVN due to the invalid certificate, it is ok now > >> Regarding the "doc" sub-sub-sub-folder I find your proposal >> counterintuitive, al least for macOS, >> The documentation should be readily available, not in a folder 3 layers down > > On MacOS there would be a directory layout for Frameworks and Applications > that Apple suggests > (therefore the layout of the Mac BSF4ooRexx installer is structured the way > it is, cf. [1], [2]). > Looking at different MacOS installations in the /Applications folder shows > that application > developers do not necessarily adhere to the Apple suggested layout. As such I > think you are free to > define any directory structure that you think is intuitive and helpful. What is „right“ on macOS is a philosophical question, I have all kinds of applications/frameworks/bundles etc on my machine, depending on when,how and by whom they were created. The macOS installer is a „hack“ in that sense, anyone with a wish to make it compliant with all the rules of Apple´s whims is more than welcome to amend the installer builder What would be much more interesting would be to get hold of an M1 based Mac for connecting to Jenkins. ~P.O. > _______________________________________________ > 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
