Could you make the installer not overwrite any installed plugins? I have changed the chat, multiple send, etc plugins and I am worried they might get overwritten. Also, if you want to send me your NSIS script I can convert it to NSIS version 2, which is shinier.
Installer
Posted by Poromenos on Tue 30 Nov 2004 10:47 PM — 8 posts, 26,599 views.
Didn't we go through this topic a while back? How do I know something has changed? Or do you just want to never overwrite? In that case, if someone hasn't changed it, and it has a bug which I fix in a later release, then they keep the buggy one forever.
I am using NSIS version 2, but I can send you the script.
Hm, maybe we did. NSIS has an "overwrite if newer" option... Could you send it to poromenos at gmail dot com, and I'll see if I can make any improvements and send it back.
I sent it, however I think we talked at some length about the "overwrite if newer" option. Dates simply don't work - what if you changed it last week, and I changed it this week? Mine is newer, yes? But reverse the order, and yours is newer. What we need to detect is *who* made the change, not when it was made.
Like I said last time, I think the only way that could work would be to do a hash of every file (as shipped) and then compare the hash to see if it is the same file. Even then it could get fiddly, as I would need to know the hash of all released versions (assuming there were more than one).
Like I said last time, I think the only way that could work would be to do a hash of every file (as shipped) and then compare the hash to see if it is the same file. Even then it could get fiddly, as I would need to know the hash of all released versions (assuming there were more than one).
I think its plenty fine as it is.
We've said not to use the default files (or at least change their name) forever, so if youve edited something, add a 2 to the filename, or something, to make sure it doesn't get overwritten.
What if something has changed that's important (nick updated something in one of his plugins) but you've changed yours as well, how would you know? What if you changed your plugin, but didnt know you had?
We've said not to use the default files (or at least change their name) forever, so if youve edited something, add a 2 to the filename, or something, to make sure it doesn't get overwritten.
What if something has changed that's important (nick updated something in one of his plugins) but you've changed yours as well, how would you know? What if you changed your plugin, but didnt know you had?
Probably the answer is: make backups.
If you have done work, and not backed it up, you have the same problem if your hard disk crashes.
If you have done work, and not backed it up, you have the same problem if your hard disk crashes.
Quote:
What if something has changed that's important (nick updated something in one of his plugins) but you've changed yours as well, how would you know?
What if something has changed that's important (nick updated something in one of his plugins) but you've changed yours as well, how would you know?
I wouldn't know either way, since if I had changed the filename I'd never open the installed one (unless I saw an announcement saying that it was changed or something).
Quote:
If you have done work, and not backed it up, you have the same problem if your hard disk crashes.
If you have done work, and not backed it up, you have the same problem if your hard disk crashes.
Yes, but I would prefer not to add installers to the risk of HDD crash :P Besides, an HDD crash is mostly recoverable (if you're using NTFS, anyway).