Description Jeff McAffer 2001-10-10 22:49:20 EDT

In addition to the normal 'workspace' directory, another, apparently unused 
directory structure is created ("ide-beta/opt/vame1.4/workspace/.metadata").  

My installation is in /opt/vame1.4.  After installation, I go into 
'/opt/vame1.4/ide-beta' and execute './vame'.  An 'opt' directory 
appears under 'ide-beta' containing a skeleton of the normal
workspace structure.

New projects are still placed under '$VAMEHOM/ide-beta/workspace'.
The extra structure under '$VAMEHOME/ide-beta/opt' doesn't seem
to be used.

NOTES:

WGR (7/27/2001 3:53:06 PM)
	Whatever directory you start in will get a structure as described above.
	E.g. if you start in '/root', you will get a '/root/root/.metadata'.  Also, when starting
	in '/root', no 'workspace' directory is created; new projects are created in the current
	directory (e.g. '/root/FooProject').

	Also, instead of using '/tmp', we seem to be creating a 'tmp' directory in the current
	directory.  So in the above example, I ended up with a '/root/tmp/platform' structure.
	Same was true when run from '/opt/vame1.4/ide-beta'.
	
KJD (7/30/2001 11:03:54 AM)
	This is a base eclipse problem please moving to the appropriate box (ITPCORE)

KJD (7/30/2001 11:12:52 AM)
	Possibly a dup of: 
		1GE8WDW: ITPCORE:Linux - duplicate dir structure created while creating .metadata


KJD (7/30/2001 11:21:51 AM)
	Here is an email from WGR:
------------------------>
		I've noted some unexpected behavior from VAME, WS WB, beta on Linux.  Brooke 
		thinks he's seen it too.  Looks kind of like it's just missing a leading "/" somewhere. 

		Also, the way I normally use VAME is to untar it as root into /opt/vame1.4 and then 
		go back to being brussell and run it from my home directory.  But on WS WB, the 
		out-of-the-box permissions (700) keep me from doing that.  I don't really want to 
		"chmod -R 777" the whole thing.  I don't think that regular users need write access 
		to anything under /opt/vame1.4.  What's your expectation here?

		Thanks,
		Bill
------------------------>

KJD (7/30/2001 11:20:42 AM)
	I believe your expectations are correct.  Alas it seems that it is a core bug.   It would 
	seem to me that 700 is too strict perhaps either 755 or 733 would be more appropriate 
	for out of the box (depending on the resolution to this PR and its dups).

	You are correct, regular users should not need write access to anything under /opt/vame1.4.  
	By default we should be creating a directory under the home directory of 
	the user (say $HOME/VAME_workspace).