I was looking into my issues with menubuilder and trying to figure out ways to make the setup automatic so that everything would go where it should (since I know how to manually make wine put things in the proper place), and I noticed that no matter how wine is invoked (wine, winecfg, wineboot, winemine, notepad etc), if there is no ~/.wine it runs wineprefixcreate _first_ in order to create it.
Currently in order to fix my issues, I have to re-run wineprefixcreate after running winecfg to make sure the directories and files are put in the place I have my fake c located.
Would it be possible to make winecfg run wineprefixcreate one more time after the ok and apply buttons are pressed so that users dont have to manually run it when they use winecfg?
On Wed, Mar 21, 2007 at 09:31:23AM -0500, Tom Spear wrote:
I was looking into my issues with menubuilder and trying to figure out ways to make the setup automatic so that everything would go where it should (since I know how to manually make wine put things in the proper place), and I noticed that no matter how wine is invoked (wine, winecfg, wineboot, winemine, notepad etc), if there is no ~/.wine it runs wineprefixcreate _first_ in order to create it.
Currently in order to fix my issues, I have to re-run wineprefixcreate after running winecfg to make sure the directories and files are put in the place I have my fake c located.
Would it be possible to make winecfg run wineprefixcreate one more time after the ok and apply buttons are pressed so that users dont have to manually run it when they use winecfg?
What do you really want to do?
Ciao, Marcus
On 3/21/07, Marcus Meissner meissner@suse.de wrote:
On Wed, Mar 21, 2007 at 09:31:23AM -0500, Tom Spear wrote:
I was looking into my issues with menubuilder and trying to figure out ways to make the setup automatic so that everything would go where it should (since I know how to manually make wine put things in the proper place), and I noticed that no matter how wine is invoked (wine, winecfg, wineboot, winemine, notepad etc), if there is no ~/.wine it runs wineprefixcreate _first_ in order to create it.
Currently in order to fix my issues, I have to re-run wineprefixcreate after running winecfg to make sure the directories and files are put in the place I have my fake c located.
Would it be possible to make winecfg run wineprefixcreate one more time after the ok and apply buttons are pressed so that users dont have to manually run it when they use winecfg?
What do you really want to do?
Well, Im just wanting to have winecfg run wineprefixcreate after the ok and apply buttons are pressed, so that the files and folders created by wineprefixcreate are created in the location of the fake c drive (in the event a user moved it from the default)..
On Wed, Mar 21, 2007 at 12:24:23PM -0500, Tom Spear wrote:
Well, Im just wanting to have winecfg run wineprefixcreate after the ok and apply buttons are pressed, so that the files and folders created by wineprefixcreate are created in the location of the fake c drive (in the event a user moved it from the default)..
But then the old location is left behind and the new used instead, what happens when the user already has something installed there?
How about a big warning that the user needs to move the content of the directories he changed himself and a pop-up warning on OK if e.g. the windows directory is not found on C: ?
Jan
On 3/21/07, Jan Zerebecki jan.wine@zerebecki.de wrote:
On Wed, Mar 21, 2007 at 12:24:23PM -0500, Tom Spear wrote:
Well, Im just wanting to have winecfg run wineprefixcreate after the ok and apply buttons are pressed, so that the files and folders created by wineprefixcreate are created in the location of the fake c drive (in the event a user moved it from the default)..
But then the old location is left behind and the new used instead, what happens when the user already has something installed there?
How about a big warning that the user needs to move the content of the directories he changed himself and a pop-up warning on OK if e.g. the windows directory is not found on C: ?
Well if we are going to do that, then we might as well move the folders to the new location for the user. Regardless, some change is better than what we have now, because this is what was causing me to have to manually create windows\system32 and Program\ Files..
"Tom Spear" speeddymon@gmail.com writes:
Well if we are going to do that, then we might as well move the folders to the new location for the user. Regardless, some change is better than what we have now, because this is what was causing me to have to manually create windows\system32 and Program\ Files..
Winecfg should probably not allow moving the C drive; if you really want that, you have to know what you are doing, and do it by hand. Why do you want to move it at all?
On 3/22/07, Alexandre Julliard julliard@winehq.org wrote:
"Tom Spear" speeddymon@gmail.com writes:
Well if we are going to do that, then we might as well move the folders to the new location for the user. Regardless, some change is better than what we have now, because this is what was causing me to have to manually create windows\system32 and Program\ Files..
Winecfg should probably not allow moving the C drive; if you really want that, you have to know what you are doing, and do it by hand. Why do you want to move it at all?
Because I have a 20gb drive that Linux is installed on, and a blank 40gb mounted at /mnt/d (there is no windows installed on it). I want wine to install its things to my 40gb, and just for no other good reason than the fact that I am making an example of a normal user, I dont want to move the 40gb from /mnt/d .. IMHO if we are going to give the users the option to put their c drive where they want to so easily, we should make assumptions that they will want anything installed there to be moved if they relocate it, or we should give them a way to setup where their c drive is located before anything is put there, instead of assuming that they want it located at ~/.wine/drive_c ..
--- Tom Spear speeddymon@gmail.com wrote:
Because I have a 20gb drive that Linux is installed on, and a blank 40gb mounted at /mnt/d (there is no windows installed on it). I want wine to install its things to my 40gb, and just for no other good reason than the fact that I am making an example of a normal user, I dont want to move the 40gb from /mnt/d .. IMHO if we are going to give the users the option to put their c drive where they want to so easily, we should make assumptions that they will want anything installed there to be moved if they relocate it, or we should give them a way to setup where their c drive is located before anything is put there, instead of assuming that they want it located at ~/.wine/drive_c ..
It seems the easiest is to have ~/.wine a symlink to some directory on /mnt/d (if possible), that "just works"
____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
On Thu, Mar 22, 2007 at 09:32:54AM -0500, Tom Spear wrote:
On 3/22/07, Alexandre Julliard julliard@winehq.org wrote:
Winecfg should probably not allow moving the C drive; if you really want that, you have to know what you are doing, and do it by hand. Why do you want to move it at all?
Yes, just too much can go wrong there, without special care.
Because I have a 20gb drive that Linux is installed on, and a blank 40gb mounted at /mnt/d (there is no windows installed on it). I want wine to install its things to my 40gb, and just for no other good reason than the fact that I am making an example of a normal user, I dont want to move the 40gb from /mnt/d .. IMHO if we are going to give the users the option to put their c drive where they want to so easily, we should make assumptions that they will want anything installed there to be moved if they relocate it, or we should give them a way to setup where their c drive is located before anything is put there, instead of assuming that they want it located at ~/.wine/drive_c ..
How about you move your .wine to /mnt/d/ and make a symlink from ~ (or set WINEPREFIX)? That sounds like a much saner solution than moving your drive_c around from within winecfg.
Jan
On 3/22/07, Jan Zerebecki jan.wine@zerebecki.de wrote:
On Thu, Mar 22, 2007 at 09:32:54AM -0500, Tom Spear wrote:
On 3/22/07, Alexandre Julliard julliard@winehq.org wrote:
Winecfg should probably not allow moving the C drive; if you really want that, you have to know what you are doing, and do it by hand. Why do you want to move it at all?
Yes, just too much can go wrong there, without special care.
Because I have a 20gb drive that Linux is installed on, and a blank 40gb mounted at /mnt/d (there is no windows installed on it). I want wine to install its things to my 40gb, and just for no other good reason than the fact that I am making an example of a normal user, I dont want to move the 40gb from /mnt/d .. IMHO if we are going to give the users the option to put their c drive where they want to so easily, we should make assumptions that they will want anything installed there to be moved if they relocate it, or we should give them a way to setup where their c drive is located before anything is put there, instead of assuming that they want it located at ~/.wine/drive_c ..
How about you move your .wine to /mnt/d/ and make a symlink from ~ (or set WINEPREFIX)? That sounds like a much saner solution than moving your drive_c around from within winecfg.
Ok, so basically what I'm getting is that as a normal user, I'm expected to know to make a symlink from ~/.wine/drive_c to /mnt/d .. That is fine for me, I have no problem doing this, but my concern is for average joe who is just starting out with linux, and doesn't know what a symlink is. They read the docs and get wine installed, install some programs, and then later on find out that they can move their wine drive_c to their secondary drive via winecfg. So they do that and then all of their apps are gone and they are like WTF? So after a lil bit of research they find out that wine didnt move their stuff, it just made a link and they either need to move the stuff themselves, or reinstall.
Wouldnt it be more sane for winecfg to make the symlink in the first place, before they install anything?
As for making a symlink from /mnt/d to ~/.wine, which one person mentioned, there are 2 problems with that.
1) Not all users want to setup their machine with their d drive mounted at ~/.wine/drive_c 2) What about multi-user installs? ~/.wine is specific to the user that ~ belongs to.
On 3/22/07, Tom Spear speeddymon@gmail.com wrote:
On 3/22/07, Jan Zerebecki jan.wine@zerebecki.de wrote:
On Thu, Mar 22, 2007 at 09:32:54AM -0500, Tom Spear wrote:
On 3/22/07, Alexandre Julliard julliard@winehq.org wrote:
Winecfg should probably not allow moving the C drive; if you really want that, you have to know what you are doing, and do it by hand. Why do you want to move it at all?
Yes, just too much can go wrong there, without special care.
Because I have a 20gb drive that Linux is installed on, and a blank 40gb mounted at /mnt/d (there is no windows installed on it). I want wine to install its things to my 40gb, and just for no other good reason than the fact that I am making an example of a normal user, I dont want to move the 40gb from /mnt/d .. IMHO if we are going to give the users the option to put their c drive where they want to so easily, we should make assumptions that they will want anything installed there to be moved if they relocate it, or we should give them a way to setup where their c drive is located before anything is put there, instead of assuming that they want it located at ~/.wine/drive_c ..
How about you move your .wine to /mnt/d/ and make a symlink from ~ (or set WINEPREFIX)? That sounds like a much saner solution than moving your drive_c around from within winecfg.
Ok, so basically what I'm getting is that as a normal user, I'm expected to know to make a symlink from ~/.wine/drive_c to /mnt/d .. That is fine for me, I have no problem doing this, but my concern is for average joe who is just starting out with linux, and doesn't know what a symlink is.
Like Alexandre said, users shouldn't be moving drive_c itself, only .wine. And if you do move drive_c, you need to know what you're doing. For the average user, moving .wine only requires changing WINEPREFIX, no symlinks needed.
They read the docs and get wine installed, install some programs, and then later on find out that they can move their wine drive_c to their secondary drive via winecfg. So they do that and then all of their apps are gone and they are like WTF? So after a lil bit of research they find out that wine didnt move their stuff, it just made a link and they either need to move the stuff themselves, or reinstall.
If they read the docs, then they'd know that WINEPREFIX takes care of all of this. Did you read the docs?
http://winehq.org/site/docs/wine
Wouldnt it be more sane for winecfg to make the symlink in the first place, before they install anything?
As for making a symlink from /mnt/d to ~/.wine, which one person mentioned, there are 2 problems with that.
- Not all users want to setup their machine with their d drive
mounted at ~/.wine/drive_c 2) What about multi-user installs? ~/.wine is specific to the user that ~ belongs to.
You're overcomplicating a situation that is simple in the first place.
On 3/22/07, James Hawkins truiken@gmail.com wrote:
Like Alexandre said, users shouldn't be moving drive_c itself, only .wine. And if you do move drive_c, you need to know what you're doing. For the average user, moving .wine only requires changing WINEPREFIX, no symlinks needed.
Ok, so then perhaps we should remove that "feature" of winecfg.
If they read the docs, then they'd know that WINEPREFIX takes care of all of this. Did you read the docs?
Not recently, no. But I have read them in the past..
On 3/22/07, Tom Spear speeddymon@gmail.com wrote:
On 3/22/07, James Hawkins truiken@gmail.com wrote:
Like Alexandre said, users shouldn't be moving drive_c itself, only .wine. And if you do move drive_c, you need to know what you're doing. For the average user, moving .wine only requires changing WINEPREFIX, no symlinks needed.
Ok, so then perhaps we should remove that "feature" of winecfg.
If they read the docs, then they'd know that WINEPREFIX takes care of all of this. Did you read the docs?
By the way, I just looked over the docs (the wine users guide anyways), and even did a search on all of winehq and the only place that WINEPREFIX came up in the search was under the mailing list archives, and I didn't see any mention of it in the user's guide.
On 3/22/07, Tom Spear speeddymon@gmail.com wrote:
On 3/22/07, Tom Spear speeddymon@gmail.com wrote:
On 3/22/07, James Hawkins truiken@gmail.com wrote:
Like Alexandre said, users shouldn't be moving drive_c itself, only .wine. And if you do move drive_c, you need to know what you're doing. For the average user, moving .wine only requires changing WINEPREFIX, no symlinks needed.
Ok, so then perhaps we should remove that "feature" of winecfg.
If they read the docs, then they'd know that WINEPREFIX takes care of all of this. Did you read the docs?
By the way, I just looked over the docs (the wine users guide anyways), and even did a search on all of winehq and the only place that WINEPREFIX came up in the search was under the mailing list archives, and I didn't see any mention of it in the user's guide.
It's right there in the link I posted. Try this google search (to avoid searching the MLs):
site:winehq.org/site/docs WINEPREFIX
-
Alexandre Julliard -
James Hawkins -
Jan Zerebecki -
Joris Huizer -
Marcus Meissner -
Tom Spear