Yup ... I see what you mean.  I did a quick search on the internet
and found that NSUserDirectory returns /Network/Users with
the Network domain mask, /Users with the User domain mask, and
nothing with the other ones.

Hmmm.

Interpreted in this way, 'NSUserDirectory' is not very useful as a concept, 
because eg in Unix systems users can have their directory anywhere on disk.
While most "normal" users will have /home/xxx as their home directories, that's
not necessarily always the case (just think of root).

Anyway I suppose in our implementation we just let people specify in their 
filesystem layout a 'location of user home directories' (by default, /home), 
store it in all the various config files, and have it returned for the 
combination
of NSUserDirectory/LocalDomain ?

Do we need to bother with a different location for the network domain, or
with a different location for each domain ?

Thanks

-----Original Message-----
From: Richard Frith-Macdonald <[EMAIL PROTECTED]>
Sent: Tue, March 6, 2007 8:34 am
To: Nicola Pero <[EMAIL PROTECTED]>
Cc: GNUstep Developer <gnustep-dev@gnu.org>
Subject: (no subject)

While looking at a bug in the way the services system was using  
NSUserDirectory and appending Library to get the user's Library  
direcdtory (which was always wrong, but used to work), I decided to  
check what MacOS-X does.

It returns /Users and /Network/Users when given the all domains mask.

So this constant should return the directories in which user's home  
directories can be found.
This is *not* what the current GNUstep implementation does.

I guess we should try to emulate MacOS-X behavior ... and I guess  
that means we need further filesystem modifications to make and  
base ... does that sound reasonable?


_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev



_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Reply via email to