[Wine] Installing Wine on MacOSX was {Re: Memory Limitations for WINE 1.1.33 under Mac OS Leopard}

[James Mckenzie]

doh123 wrote about Installing Wine on MacOSX was {Re: Memory Limitations for WINE 1.1.33 under Mac OS Leopard}
>
>James Mckenzie wrote:
>> doh123 wrote:
>> Except 'make install' puts files in /usr/bin and /usr/lib, not in the /Applications folder with vanilla Wine.  I'm hoping that is not what we are discussing here.
>> 
>
>which files?  I install to a custom prefix all the time and move it computer to computer and use it.. never messed with anything in /usr/bin and /usr/lib... and Wine works fine.
>
Wine, by default on any UNIX will install to either /usr or /usr/local.  I've installed it on Linux and this is where the binaries and library files go.  Vanilla Wine, compiled on MacOSX with dependencies installed, will install to /usr/local/wine and then symlink into /usr/bin.  This makes removal a real fun task.  That is why I like using .app packages.  Everything goes into the package excepting local settings and user files (/Library/Application Support/<insert program name here> and ~/<insert program name here>.
>
>James Mckenzie wrote:
>> 
>> Most files in /Applications are owned by root:bin or root:root and have read/execute permissions for other users.
>> 
>
>Some are root (macports does this...), most actually aren't.  The folder is open for all users to read/write to, with full access.
>
Hmmm.  Let me check that.  I think my /Applications folder has most files owned by root or me (I am administrative user).  I'll also correct that the files are mostly owned by root:admin or <user name>:admin.  However, the files still have rwxr-xr-x (me) or rwxrwxr-x (root) which means that any user can run the programs.  Utilities are another matter, as some of those programs can only be run by members of the admin group, which is 'good thing' because you don't want just any user running things like the Disk Utility.

That being said, the problem is that you have to be an administrative user, or have an administrative user's credentials to install a program on a Mac.  So, the question still remains, if I use an installer, can I just as easily remove a program I no longer want or use?  I know with a .app install, I remove the program from the /Applications folder, remove any user files (.wine in this case) and if necessary, any files in /Library and /Library/Application Support and I'm done, finished and all traces of the program are essentially removed.  With an installer, files can and do go everywhere (take a look at Adobe Acrobat Reader for a good example.)  'Well behaved' MacOSX programs do have an de-installation plan and this should be enforced through some sort of de-installation process.

BTW, I've been through the .app versus the installer saga before.  I'll advise that the .app routine was used for a while.  I don't know the status of the program as I left the project just after it was 'taken over' and decisions are now made outside of the development teams control.


>
>James Mckenzie wrote:
>> 
>> Will this allow a 'clean' de-installation of the program if the user does not want to keep it around?
>
>if it installs like normal Mac apps to everything in a single folder in /Applications... yes, you just remove the folder.
>
>
>
>
>