Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Suggestions
➜ Mushclient setup suggestion
|
Mushclient setup suggestion
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Poromenos
Greece (1,037 posts) Bio
|
| Date
| Fri 11 Apr 2003 11:26 AM (UTC) |
| Message
| | MUSHClient setup should not overwrite scripts, figlet files, or generally anything that hasn't changed, or that the user could have changed, at least not without prompting... I hate how it replaces the custom multiple_send.xml every time... |
Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it! | | Top |
|
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Sat 12 Apr 2003 08:26 AM (UTC) |
| Message
| I think we went through this one a while back. You say it shouldn't overwrite things that the user changed - fair enough, but how do we know the user changed it?
Say the original file was installed in January, you changed it in February, and the new file (from the install) was changed in March. The installer looks at the file and says "I am replacing an earlier file, that is OK".
The only real way to know if *you* changed it would be to have a list of hashes for every file previously installed, and then hashes for the new ones, and warn the user if we appear to be replacing a file whose hash we don't know of. This could get quite complex if the MUSHclient files (eg., scripts) change quite often, but you don't necessarily install every version.
As for warning before replacing every file, that would be tedious. If you can give me an algorithm that you think would work (in pseudo-code) let me know. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Linda
Sweden (164 posts) Bio
|
| Date
| Reply #2 on Sat 12 Apr 2003 06:35 PM (UTC) |
| Message
| | Wouldn't it be possible to, in addition to the version that uses the installer, for each new release of MUSHclient also distribute a zip file that contains only those elements updated for that release? | | Top |
|
| Posted by
| Poromenos
Greece (1,037 posts) Bio
|
| Date
| Reply #3 on Sat 12 Apr 2003 08:57 PM (UTC) |
| Message
| Linda, the installer is very small, and the other files are too, so a zip file wouldn't really make a difference, maybe 30-40 kb?
Nick, about that suggestion, it's simple... Just update mushclient.exe and any DLLs or files that the user can't customize, and if the file dates are different for the rest of the files, ask. That way, if i changed a plugin, it would prompt me, otherwise it would overwrite/do nothing, because the files would be the same... NSIS can do that... Also, you should set "SetDateSave on" if you haven't, it helps. |
Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it! | | Top |
|
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #4 on Sat 12 Apr 2003 09:43 PM (UTC) |
| Message
| | SetDateSave is on, however I don't see how that helps. I still can't distinguish between a batch of files *I* have changed and a batch of files *you* have changed. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #5 on Sat 12 Apr 2003 09:45 PM (UTC) |
| Message
| To anyone reading this, I recommend that if you plan to change a supplied file from the MUSHclient distribution (eg. sample script files, sample plugins, or whatever) you make a copy under a different name, and use the copy. That way it can't be overridden.
To be paranoid you would also put it into a different directory in case you choose a name I later use myself. This has the added advantage that you can tell which are your files, because they are in a different directory. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Linda
Sweden (164 posts) Bio
|
| Date
| Reply #6 on Sun 13 Apr 2003 12:08 PM (UTC) |
| Message
| | I wasn't suggesting a zip to cut down on size, just so you don't have to be concerned about files being overwritten. I'd just like to be able to extract only the files that were updated for that release. | | Top |
|
| Posted by
| Poromenos
Greece (1,037 posts) Bio
|
| Date
| Reply #7 on Sun 13 Apr 2003 06:15 PM (UTC) Amended on Sun 13 Apr 2003 06:21 PM (UTC) by Poromenos
|
| Message
| | Make it ask the user when the source file's date is different from the destination file's, except for mushclient.exe or the .dlls. With setdatesave on, the dates of the unchanged files of each release will be the same, so it would ask the user before overwriting files, even if you had changed them... |
Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it! | | Top |
|
| Posted by
| Haflinger
(9 posts) Bio
|
| Date
| Reply #8 on Sun 20 Apr 2003 03:11 AM (UTC) |
| Message
| I think what Linda was suggesting, was having the installer create a subdirectory in MUSHclient, possibly named "Update", and extract all the files there. Then one could selectively copy the files from that directory, into the MUSHclient directory. This is assuming that the files to be copied don't have to be "installed" into the registery or integrated into another file somehow.
| | Top |
|
| Posted by
| Flannel
USA (1,230 posts) Bio
|
| Date
| Reply #9 on Sun 20 Apr 2003 04:44 AM (UTC) |
| Message
| What Nick is saying is, when you edit a file, Rename it, that way it wont get overwriten, as well as you'll know that its YOUR file. There's no reason to make a 'smart installer' when you can just have smart operators. Cuts down on bloat, and makes things run more smoothly and clearly.
|
~Flannel
Messiah of Rose
Eternity's Trials.
Clones are people two. | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
32,456 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top