You raise a point I have been thinking about and your comment about 3 parts:
immutable system, extensions, user
makes some sense.
This suggests a minor tweak to our current layout which is to add addons to
the user folder. This would remove the admin requirement for using JAL for
addons. But
:[EMAIL PROTECTED] On Behalf Of Oleg Kobchenko
Sent: Friday, 5 October 2007 09:32
To: Beta forum
Subject: Re: [Jbeta] J install folders and JAL
It might be good to talk about use cases (what different
locations) and features (ability to support different
locations for different things: system
--Oleg Kobchenko wrote:
It seems the use cases can be fit into cross-platform
equivalencies:
- immutable, admin-level locations:
Program Files; Applications and .app; /usr/lib
I'm very new to Linux but would it be more appropriate for the above to
be /usr/local/lib rather than /usr/lib
The original reference was for Mac OSX which doesn't
have (by default) a /usr/local/ directory. However, it
is easy for a user to add one (although then one wants
to augment /etc/bashrc to include it in $PATH) - in Linux,
I agree jsoftware should use /usr/local/lib
- joey
At 11:20 +1300
On 10/4/07, Sherlock, Ric [EMAIL PROTECTED] wrote:
Are the problems resolved if the user installs with J with Admin rights
if they choose to do an immutable method install?
There's probably an issue of which admin rights.
Windows security permissions are very fine-grained, and error
reporting
---Raul Miller wrote:
On 10/4/07, Sherlock, Ric wrote:
Are the problems resolved if the user installs with J with Admin
rights if they choose to do an immutable method install?
There's probably an issue of which admin rights.
Windows security permissions are very fine-grained, and
