wine overstepping the mark?

wino at wino at
Thu Oct 27 18:04:05 CDT 2005

Thanks for the explaination but that's just my point. That is windows  
mentality, but this is not windows.

If I install gimp it does not try to reconfigure my system and take over  
control of any image file types it can handle. That is windows mentality.

What it is does is the first time it is run it _asks_ me if I wish to  
associalte it with certain file types and depending on the response it  
sets some preference _for that user_.

If I then start gimp as another user it has no knowlege of this and asks  
the same questions : for that user.

What I am trying to suggest here is that spending too long , too close to  
windows code it can be infectious. I am trying to raise a little reminder  
of where we are here. Linuxland not Billville.

> If you have ever tried to click on an executable ...
A .exe is not an "executable" on this system. You cannot "click" on a  
file, a file is data on a disk. You may click on a filename displayed in a  
filemanager at which point I would expect it to execute the program , if  
any , I have associtated with that file type. If I have installed new  
software I may need to alter that setting.

> your GUI shows you the action that it is running the file,

Does it? What GUI is that? Are refering to a window manager, a desktop  
environment or a file manager ??

If it does as you say , your particular GUI is broken I suggest you try  
another that behaves correctly.

OK, I wont labour the point any more.

If installing wine is messing with global config files , it should not be.


On Thu, 27 Oct 2005 22:53:19 +0200, Dustin Navea <speeddymon at>  

> I think I mis-worded what I was trying to say..  I believe that the  
> mimetypes have to be updated specifically for the .exe binaries.  If you  
> have ever tried to click on an executable when wine is not installed,  
> your GUI shows you the action that it is running the file, but it  
> doesn't do anything (because wine isnt installed, and the gui can't run  
> PE binaries, only aout and elf ones)..  So wine has to update the  
> mimetype for exe's, so that when you double click on one, it does the  
> same as opening a console and typing "wine filename.exe"..
> Hope that clears up what I was trying to say previously.
> Dustin
> wino at wrote:
>> On Thu, 27 Oct 2005 21:23:48 +0200, Dustin Navea  
>> <speeddymon at>  wrote:
>>> I dont see how that is a problem?  AFAIK wine has to mod them so that   
>>> when you double click on an exe in your GUI, the GUI knows what  
>>> program  to load the exe's with...  but then again I could be wrong.   
>>> anyone else?
>>> Dustin
>>  Well that's why the sandbox is there.
>>  I install Wine for one specific user account that has suitably  
>> restricted  access rights. I do not want wine or wine installer to go  
>> outside that  brief.
>>  I want wine on this system so that I can use on or two bits of  
>> windows  software , I DO NOT want it to start thinking it really IS  
>> windows and  start taking over my computer for me.
>>  That is the fundamental reason why I use Linux and not M$.

More information about the wine-devel mailing list