Open Object Rexx Support Requests 8 Oorexx For Mac
You can subscribe to this list. On 21:59, David Ashley wrote: Mark is absolutely correct in feeling that installing packages inside other packages is a big no-no.
It violates the Linux file system standard (Lbig time. I would suggest that BSF4Rexx be installed directly in /opt/BSF4Rexx and that is should make no modifications to anything in any other package.
If you notice ooRexx creates links from files in the /opt/ooRexx subdirectory tree to /usr/bin and /usr/lib. This is the recommendation of the file system standard. There may be dependencies that are impacted causing applications not to function when one package is removed but files will not be impacted. Thanks David and Mark! Mark is absolutely correct in feeling that installing packages inside other packages is a big no-no. It violates the Linux file system standard (Lbig time.
I would suggest that BSF4Rexx be installed directly in /opt/BSF4Rexx and that is should make no modifications to anything in any other package. If you notice ooRexx creates links from files in the /opt/ooRexx subdirectory tree to /usr/bin and /usr/lib. This is the recommendation of the file system standard. There may be dependencies that are impacted causing applications not to function when one package is removed but files will not be impacted. David Ashley This is all done this way so that any package does not impact the install or removal of another package. There may be On 02:03 PM, Mark Miesfeld wrote: On Mon, Aug 2, 2010 at 11:28 AM, Rony G.
Flatscher wrote: t On 20:14, CVBruce wrote: I know that I wrote the ooRexx V4.0.1 scripts for MacOS preflight and postflight to touch only the things that were ooRexx. They will not remove BSF4Rexx if present. Hmm, then this is about the install/deinstall scripts of the providers (hence the ooRexx responsible persons)?
I know that the current debian and rpm packages delete everything under /opt/oorexx. That's why I asked if you had tested. There is no changing of that for 4.0.1. It is possible that you could get this changed in a future release.
However, it's the way it has been done for some time. We can see what David thinks, I don't pay much attention to what the 'standard way' to do things on Linux is. But, from the stand point of a user that often needs to get things done on Linux, my 2 cents is that installing a package in a subdirectory of some other package does not feel right to me.
- Mark Miesfeld - The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: Oorexx-devel mailing list Oorexx-devel@. Hi Bruce, On 20:46, CVBruce wrote: 1. I guess I'm that person.
I modified the preflight and postflight scripts from ooRexx V3.2 I added in the necessary stuff to get the rxapi daemon running. I chose not to touch anything other than ooRexx, just incase BSF4Rexx was installed under /opt/ooRexx, as was done in ooRexx V3.2.
AFAIK BSF4Rexx on Mac got only installed with ooRexx. Hence uninstalling ooRexx on the Mac should uninstall BSF4Rexx as well. Ad ooRexx 4.0.1 and BSF4Rexx: BSF4Rexx should not be run with ooRexx 4.0.1. (OTOH BSF4ooRexx needs ooRexx 4.0.1 as it interacts with the new ooRexx C APIs, which get extensively used.) Rather 'BSF4ooRexx.cc' should be compiled for the different MacOSX platforms (the MAC switches from BSF4Rexx remained intact in the new BSF4ooRexx.cc). Everything else is Java or Rexx and can be used/packaged unchanged from the other distributions. Of course, if you try to tackle that I would be there to help on BSF4ooRexx whatever I can (not having a Mac, there is unfortunately not more than I can do currently). I have running versions of ooRexx V4.0.1 for i386, x8464, and ppc.
They all seem to work on my MacBook Pro under Mac OS X 10.5.8 (Leopard). They at least pass the testOORexx.rex script. In fact the only way I can tell which one is running is to look in Activity Monitor. That sounds already great and very useful! My real problem is that I'm having a terrible time trying to package them.
I keep ending up with a package that wants to install in / or / ooRexx, rather than /opt/ooRexx. I don't think people would like having the package installed in the wrong place. Also I'm trying to get 4.0.1 to compile on Tiger, Mac OS X 10.4, so that more people can use it. I haven't tested it on 10.6 (Snow Leopard), and will do that. Sorry, that I can not be of any help here. On 21:03, Mark Miesfeld wrote: On Mon, Aug 2, 2010 at 11:28 AM, Rony G. Flatscher wrote: On 20:14, CVBruce wrote: I know that I wrote the ooRexx V4.0.1 scripts for MacOS preflight and postflight to touch only the things that were ooRexx.
They will not remove BSF4Rexx if present. Hmm, then this is about the install/deinstall scripts of the providers (hence the ooRexx responsible persons)? I know that the current debian and rpm packages delete everything under /opt/oorexx. That's why I asked if you had tested. Well, creating an own /opt/bsf4oorexx branch seems to be as easy, if not easier. On Mon, Aug 2, 2010 at 11:28 AM, Rony G. Flatscher wrote: On 20:14, CVBruce wrote: I know that I wrote the ooRexx V4.0.1 scripts for MacOS preflight and postflight to touch only the things that were ooRexx.
They will not remove BSF4Rexx if present. Hmm, then this is about the install/deinstall scripts of the providers (hence the ooRexx responsible persons)? I know that the current debian and rpm packages delete everything under /opt/oorexx.
That's why I asked if you had tested. There is no changing of that for 4.0.1. It is possible that you could get this changed in a future release.
However, it's the way it has been done for some time. We can see what David thinks, I don't pay much attention to what the 'standard way' to do things on Linux is. But, from the stand point of a user that often needs to get things done on Linux, my 2 cents is that installing a package in a subdirectory of some other package does not feel right to me. Mark Miesfeld.
I guess I'm that person. I modified the preflight and postflight scripts from ooRexx V3.2 I added in the necessary stuff to get the rxapi daemon running. I chose not to touch anything other than ooRexx, just incase BSF4Rexx was installed under /opt/ooRexx, as was done in ooRexx V3.2.
I have running versions of ooRexx V4.0.1 for i386, x8464, and ppc. They all seem to work on my MacBook Pro under Mac OS X 10.5.8 (Leopard). They at least pass the testOORexx.rex script. In fact the only way I can tell which one is running is to look in Activity Monitor. My real problem is that I'm having a terrible time trying to package them. I keep ending up with a package that wants to install in / or / ooRexx, rather than /opt/ooRexx. I don't think people would like having the package installed in the wrong place.
Also I'm trying to get 4.0.1 to compile on Tiger, Mac OS X 10.4, so that more people can use it. I haven't tested it on 10.6 (Snow Leopard), and will do that.
Bruce On Aug 2, 2010, at 11:28 AM, Rony G. Flatscher wrote: On 20:14, CVBruce wrote: I know that I wrote the ooRexx V4.0.1 scripts for MacOS preflight and postflight to touch only the things that were ooRexx.
They will not remove BSF4Rexx if present. Hmm, then this is about the install/deinstall scripts of the providers (hence the ooRexx responsible persons)? I know that the version 3.2 ooRexx install for MacOS included BSF4Rexx. Any chances that you would be able to try a compile of 4.0.1 for MacOS?
-rony - The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: Oorexx-devel mailing list Oorexx-devel@. I know that I wrote the ooRexx V4.0.1 scripts for MacOS preflight and postflight to touch only the things that were ooRexx. They will not remove BSF4Rexx if present. I know that the version 3.2 ooRexx install for MacOS included BSF4Rexx.
Bruce On Aug 2, 2010, at 10:13 AM, Mark Miesfeld wrote: Did you test that it wouldn't get deleted if ooRexx is uninstalled? Other than that, maybe it would be better to try and guage if users would want it installed that way? As a user, I don't think I would. - Mark Miesfeld On Mon, Aug 2, 2010 at 9:49 AM, Rony G. Flatscher wrote: Hi thereexperimenting with the Linux installation of BSF4ooRexx I am wondering whether it was o.k. For everyone if I would install BSF4ooRexx as the subdirectory '/opt/ooRexx/bsf4oorexx'?
This way the new vesions of BSF4ooRexx would be located in a firmly defined directory, controlled by the directory ooRexx gets installed to. Any comments? TIA-rony - The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: Oorexx-devel mailing list Oorexx-devel@. - The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: Oorexx-devel mailing list Oorexx-devel@. Did you test that it wouldn't get deleted if ooRexx is uninstalled?
Other than that, maybe it would be better to try and guage if users would want it installed that way? As a user, I don't think I would. Mark Miesfeld On Mon, Aug 2, 2010 at 9:49 AM, Rony G. Flatscher wrote: Hi thereexperimenting with the Linux installation of BSF4ooRexx I am wondering whether it was o.k. For everyone if I would install BSF4ooRexx as the subdirectory '/opt/ooRexx/bsf4oorexx'? This way the new vesions of BSF4ooRexx would be located in a firmly defined directory, controlled by the directory ooRexx gets installed to.
Any comments? TIA-rony - The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: Oorexx-devel mailing list Oorexx-devel@.
Open Object Rexx Support Requests 8 Oorexx For Mac Free
Technology/Operating System Report Technology/Operating System Report The following table displays a list of approved Technologies that are associated with approved Operating Systems.