Henry - I agree with the idea of installing J to
generic, rather than release-specific, directories.
However, installing it at the root is "so last millenium". I'm pretty sure
all major OSs have conventions about where software gets installed. I
personally dislike the Windows high-level names because they are
long, poorly named ("Program Files"? what is on my disk that is _not_ a
file?), and have embedded spaces but I use them anyway. Also, J has
sufficient flexibility that I can keep my own code in a "~User" area not
under "Program Files", as is more convenient for backups, etc.
As far as uniformly installing J, would it work to install and customize it
one one machine, then zip up this installation to copy to the target
machines?
Good luck,
Devon
Henry Rich wrote:
> I am trying to plan how to install J602 on all 50 machines I
> have J on at school. I want a system that will work for
> 602, and then 603, etc until something fundamental changes.
>
> What I want is something that I can automate, so that a single
> batch file does the job.
> ...
> I think what I want is the following:
...
> 1. Support for installing into C:\J rather than C:\J602.
> It appears that I can work around this by installing somewhere
> & then moving the files, but I can't for the life of me
> see why the install shouldn't just install where I say to.
>
> 2. I see no reason for the ~user directory to end with
> 'j602-user' (or 'j64-602-user'). This will just create a
> headache when 603 comes along, and all the user scripts and
...
> It seems to be a big deal for Jsoftware to distinguish the
> different releases in the directory paths, but for at least
> some users we want to hide the release changes as much as
> possible.
...
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
