Re: [Oorexx-devel] [DISCUSS] Windows ooRexx Installer

[Bill T. W. <wb...@ar...>]

At the explorer post, we put all finalized rexx execs in "c:\rexx" and 
put many data files in "C:\rexx\rexxdata"

These two comventions were adopted with the very early versions of the 
rexx interpreters and the names were selected to minimize parsing problems
with file names containing blanks.  (Many of our rexx execs were passed 
optional file names on the command line.)

As windows file "permissions" have been improved over the years, this 
naming convention continued to work, while allowing multiple users on the
same computer to keep "other users" out of their directories.  Each user 
also has a "rexx" directory in "my documents" that was automattically 
added to
the environmental "PATH" varable when new user ids were created.  (We 
had 20 to 50 members and 8-10 workstations...)

Sahananda's "MY REXX" works for me, but please also consider having a 
"system wide" directory that can also be automatically searched.
It would greatly simply installation on non technical users machines.

/s/ Bill Turner, wb4alm



Sahananda (Jon) Wolfers wrote:
> Absolutely!  Maybe the Windows installer should create a 'My Rexx 
> Scripts' folder under the 'My Documents' folder and add it to the 
> path?  I get the impression that something similar happens for a 
> directory under 'bin' in linux?
>
> Jon
>
> On 14/10/2007, *Rick McGuire* <obj...@gm... 
> <mailto:obj...@gm...>> wrote:
>
>     Well, it would be friendly if that recommended place was also
>     added to the path by the installer. 
>
>     Rick
>
>     On 10/14/07, *Sahananda (Jon) Wolfers* < sah...@wi...
>     <mailto:sah...@wi...>> wrote:
>
>         What's more, I don't think that the problem was so much that
>         the uninstaller deleted the files.  More that it did it
>         unexpectedly (ie: the previous versions had been kinder).
>
>         I still think that it would be good to have a paragraph in the
>         UG explaining that code does not need to be placed with the
>         interpreter and suggesting where to place it on the different
>         platforms.
>
>         Jon
>
>         On 14/10/2007, *Rick McGuire* < obj...@gm...
>         <mailto:obj...@gm...>> wrote:
>
>             It's generally considered inappropriate for Windows
>             applications to store anything other than installed files
>             in its program files directory.  A more appropropriate
>             place would be the Application Data directory OR create a
>             directory in My Documents.  Once you're talking about
>             having an extra directory added to the path, then it
>             should be in an appropriate location. 
>
>             The installer source is located in
>             platform\windows\oorexx.nsi
>
>             Rick
>
>
>             On 10/14/07, * Lee Peedin* <le...@sa...
>             <mailto:le...@sa...>> wrote:
>
>                 Over the years several have complained that an
>                 uninstall of ooRexx or a new install over an existing
>                 install wipes out any files/folders the user may have
>                 placed in the Rexx_Home path.
>
>                 I imagine it would be quite a task for the installer
>                 to maintain a list of files/folders that it
>                 creates/populates and then only remove the
>                 files/folders in this list on an uninstall.
>
>                 So, I'm interested in any comments on the following:
>
>                 For the sake of conversation, lets assume that the
>                 installation path is c:\program files\oorexx.
>
>                 Have the installer create a folder "c:\program
>                 files\oorexxExtras" and place that folder in the path
>                 'before' c:\program files\oorexx.  Include in the
>                 readme file strict instructions to the user that
>                 anything they wish to preserve on an
>                 uninstall/reinstall should be placed in this
>                 folder.  Of course
>                 the installer would NOT touch this folder on an
>                 uninstall/reinstall.
>
>                 Thoughts (including alternatives) appreciated.
>
>                 BTW: Where does one find the source code for the
>                 current Windows installer.  Is it in the current
>                 SVN tree?
>
>                 Lee
>