On Sunday, January 12, 2003, at 11:21 AM, Bill Bumgarner wrote:
What I meant by this is that it's a "user interface" issue. The user *expects* to be able to move it. The user doesn't expect to move anything in /sw/bin because it doesn't have a pretty icon and it's that weird "unix" stuff that they know they're not supposed to mess with. When you put mac applications in the mix, it changes the user's expectation.Right, they work fine everywhere. What would stop a user from moving it out of /sw/Applications? In fact, I would expect users to go "I want all of my apps in one place", and move them into /Applications, first thing they do...Because they are owned by root and the directory is not writable by the user.
If the user does that, they lose. Just like they lose if they move any other App. The user should create aliases.
At this point, though, the point is moot. It sounds like some variation of the symlink thing will work -- at least well enough.
Think of it this way: in a network computing environment (or any other multiuser environment), apps should be controlled/installed by the administrator. They should not be moved by the user. The user might copy the wrapper, they might create symlinks, but that's it...Right, but the other 95% of the mac-using world doesn't think "in a network computing environment". I'm not saying you're wrong, I understand what you mean, and if I was running a centrally administrated networked computing environment I'd be thinking about those issues too. What I'm saying that most other mac users will not expect what you're expecting, and not even know to think of it.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
