|
From: | Holger |
Subject: | Re: [Bug-gnubg] .gnubgautorc under windows |
Date: | Wed, 15 Oct 2003 19:53:02 +0200 |
At 23:19 13.10.2003, Holger wrote:
At 22:04 13.10.2003, Joern Thyssen wrote:> >I suggest the following: > > > >gnubg read and writes .gnubgautorc, .gnubg/* to/from > > > >(a) HOME on posix systems > >(b) USERPROFILE on later windows versions > >(c) current directory otherwise
What do you propose then? I think it's a severe requirement that the user must be logged on as super user!Hmm, let's see. Well, first, logged in as administrator doesn't help and actually brings problems. %USERPROFILE% would then be the one of the administrator, not the user's. Also, user permissions are enough. Every user has in his %USERPROFILE% full permissions.My suggestion is something like this: If env. var. USERPROFILE exists if directory %USERPROFILE%\gnubg doesn't exist mkdir %USERPROFILE%\gnubg if directory %USERPROFILE%\gnubg exists set it as homedirectory else homedirectory = "." or = datadirectory
Another option might be to create user directories like <gnubg install folder>\.gnubg\username.
Advantages: - no scattered directories, everything under one tree- no problems due to mutiple gnubg installations/versions that access the same prefs
Disadvantages:- maybe insufficient user rights in gnubg's install folder (but not really a problem since easily rounded) - no automatic prevention from one user seeing/editing other user's pref files (on the other hand the %USERPROFILE% tree only has full access by this user and no access by anybody else)
Regards,Holger
[Prev in Thread] | Current Thread | [Next in Thread] |