I just came across another idea that might be nice, and would be trivial to accomplish
After running ./configure the configure script tells you to run make depends && make
After that, there is nothing telling you what to do..
Obviously most users can figure out to run make install, but it would be nice to have a prompt to say "Now it is time to install wine by running 'make install' as root"
Then after that is complete, and this is where I always forget, a prompt to run wineprefixcreate and winecfg would be nice, because that seems to cause several duplicate and unnecessary bugs to be filed. Obviously the user should read documentation, but once you have read it you generally dont tend to read it again, and might forget something. I forget to run both wineprefixcreate and winecfg nearly every time I do a clean reinstall of wine because it isnt part of a normal build routine for most linux apps to have to do this..
I could write up patches for this but I'm taking off for the weekend and wont have access to my linux machine till monday morning, and also I dont know enough about automake and autoconf to be able to write that stuff in.
On 3/16/07, Tom Spear speeddymon@gmail.com wrote:
I just came across another idea that might be nice, and would be trivial to accomplish
After running ./configure the configure script tells you to run make depends && make
After that, there is nothing telling you what to do..
Obviously most users can figure out to run make install, but it would be nice to have a prompt to say "Now it is time to install wine by running 'make install' as root"
If most users know what to do, what's the point of spamming them? Also, not everyone wants to install after a build. A lot of people run wine from the build tree. If a user is not familiar enough with the standard source build process to know that he should 'make install', then he should probably be installing from rpm in the first place.
Then after that is complete, and this is where I always forget, a prompt to run wineprefixcreate and winecfg would be nice, because that seems to cause several duplicate and unnecessary bugs to be filed. Obviously the user should read documentation, but once you have read it you generally dont tend to read it again, and might forget something. I forget to run both wineprefixcreate and winecfg nearly every time I do a clean reinstall of wine because it isnt part of a normal build routine for most linux apps to have to do this..
Running winecfg/wineprefixcreate isn't a part of the build routine, and I've never seen a build routine that said, now run our application using 'xyz'. This is the same thing. It doesn't even make sense in the first place though. If you run wine and there is no existing directory at WINEPREFIX, then wineprefixcreate is run automatically. If the user already has a directory at WINEPREFIX and they run wineprefixcreate, nothing happens. So in either one of these situations, telling the user after they've built wine to run wineprefixcreate will not make a difference.
I could write up patches for this but I'm taking off for the weekend and wont have access to my linux machine till monday morning, and also I dont know enough about automake and autoconf to be able to write that stuff in.
-- Thanks
Tom
Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet!
http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-ema...
Running winecfg/wineprefixcreate isn't a part of the build routine, and I've never seen a build routine that said, now run our application using 'xyz'. This is the same thing. It doesn't even make sense in the first place though. If you run wine and there is no existing directory at WINEPREFIX, then wineprefixcreate is run automatically. If the user already has a directory at WINEPREFIX and they run wineprefixcreate, nothing happens. So in either one of these situations, telling the user after they've built wine to run wineprefixcreate will not make a difference.
That's not true. wineprefixcreate does more than just create ~/.wine, it also does some registry stuff (such as running regsvr32 on some dlls) and installs the 'fake' dlls.
Though it is generally a good idea to clean your registry every once in a while, and to do that I just run a script with:
rm ~/.wine/*.reg wineprefixcreate for i in ~/reg-exports/*.reg ; do regedit "$i" ; done
That deletes and recreates the registry (while leaving my drive mappings alone), then reapplies specific registry exports stored in ~/reg-exports (such as specific program settings, or registry-sensitive programs I don't want to reinstall).
On 3/16/07, James Hawkins truiken@gmail.com wrote:
On 3/16/07, Tom Spear speeddymon@gmail.com wrote:
[-snip-]
If most users know what to do, what's the point of spamming them? Also, not everyone wants to install after a build. A lot of people run wine from the build tree. If a user is not familiar enough with the standard source build process to know that he should 'make install', then he should probably be installing from rpm in the first place.
Granted there are people who dont want to install, and who do run directly from the build tree, however the people that do that are:
1) Most likely a developer, not a user 2) Knowingly doing so at their own risk, and that if something breaks they are responsible for fixing it and 3) not everyone uses a RH or Debian-based distro, and so not everyone has access to install deb's or rpm's..
Regardless a message to install is just a message (not as if we are forcibly installing), and it is only an idea mainly for consistency.
[-snip-]
Running winecfg/wineprefixcreate isn't a part of the build routine, and I've never seen a build routine that said, now run our application using 'xyz'. This is the same thing. It doesn't even make sense in the first place though. If you run wine and there is no existing directory at WINEPREFIX, then wineprefixcreate is run automatically. If the user already has a directory at WINEPREFIX and they run wineprefixcreate, nothing happens. So in either one of these situations, telling the user after they've built wine to run wineprefixcreate will not make a difference.
Running winecfg and wineprefixcreate is not part of the build routine, but it is recommended by the developers in 90-99% of all installs for regular users. wineprefixcreate does not get run automatically. wine does some similar things itself, but it doesnt do everything that wineprefixcreate does, and that breaks things that ordinarily would work.
winecfg is also not required as wine builds the drives etc, but running it allows the user to setup their sound (which most users want), and allows them to put their drives where they want to. [-snip-]
-- James Hawkins
wine is about choice isnt it? People dont have to take our advice and install, or run winecfg/wineprefixcreate, but if that message is there then it cuts down on bugs that are the result of users not knowing or (like me) forgetting to do so..
-
Chris Robinson -
James Hawkins -
Tom Spear