Hi there,
experimenting 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
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
On 02.08.2010 19:13, Mark Miesfeld wrote:
Did you test that it wouldn't get deleted if ooRexx is uninstalled?
No, thought dpkg was as nice as the latest ooRexx packages, but it is
not. Everything gets wiped out, if running complete deinstall.
So never mind, that's not a solution I could
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
On 02.08.2010 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.
Oops, almost forgot to ask: is there (somewhere) a version of ooRexx
4.0.1 for MacOS that people could download from?
---rony
On 02.08.2010 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
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.
On Mon, Aug 2, 2010 at 11:28 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
On 02.08.2010 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.
On 02.08.2010 21:03, Mark Miesfeld wrote:
On Mon, Aug 2, 2010 at 11:28 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
On 02.08.2010 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
Hi Bruce,
On 02.08.2010 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
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
On 02.08.2010 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
12 matches
Mail list logo
