Proper profile updating! Yay!!!!

fixes #48

CHANGELOG.md

@@ -1,25 +1,52 @@
 # devel
 
+A bug fix release turned major version update. That’s something new.
+
 **Note**: Since 2.0.1 you are probably seeing a warning about the profiles 
 having been created with a newer VoiceAttack version. I am currently alpha 
 testing a VoiceAttack build containing a bug fix. You should be able to safely 
 ignore that message :)
 
-Updated the “Updating” instructions in the README. Sadly it’s a bit more 
+**BREAKING CHANGE IN ALL PROFILES**:
-convoluted in practice than just “import the new profile package”.
 
-I have submitted a feature request on the VA formus to make it less of a hassle 
+The profiles now contain flags that will make them overwrite the current version 
-in the future. Until there’s a better way I will include all profiles that have 
+if you import them, streamlining the update process and making it work like 
-been updated on the release pages in addition to the profile package. That way 
+I expected it to work in the first place.
-you only have to go through the process of deleting the old profile, importing 
-the new one and fixing the includes for profiles that have actually changed.
 
-## EliteDangerous 6.0.2
+In order for this to work properly in the future, you need to do the following 
+steps _once_ when updating to this version:
+
+1. Keep track of which of your profiles import any of my profiles and which 
+   ones.
+1. Delete all of my profiles from VoiceAttack (`EliteDangerous`, `RatAttack`, 
+   `SpanshAttack`, `StreamAttack`). Technically also `SealAttack`, but since 
+   I am not currently including this you might want to keep it around if you are 
+   actually using it.
+1. Import the updated profiles, either manually or in the way described under 
+   “Updating” in the README.
+1. Fix all profiles that include the updated profiles. You are going to have to 
+   re-add the includes (“Edit Profile” → “Options” → “Include commands from
+   other profiles”).
+1. If you haven’t yet created your own custom profile and imported mine there, 
+   a) do that now for the future and b) you’ll have to re-configure any settings 
+   you have changed either through voice commands or fiddling with commands 
+   manually (don’t do the latter, please).
+
+In the future you will be able to update to new version of my profiles by simply 
+dropping the profile package into your VoiceAttack’s `\Apps\Import` subfolder, 
+as described in the README.
+
+## EliteDangerous 7.0
 
 ### Added
 
 * Parameterized `EliteDangerous.openSystemOnEdsm` command
 
+### Changed
+
+* Is now set up to overwrite an old version on import. See “Updating” 
+  instructions in the README.
+
 ### Fixed
 
 * `Route details event` now only firing when it should, not on automated 
@@ -35,7 +62,12 @@ the new one and fixing the includes for profiles that have actually changed.
 * `EliteDangerous.openCurrentSystemOnEdsm`, 
   `EliteDangerous.openCopiedSystemOnEdsm`
 
-## RatAttack 4.0.2
+## RatAttack 5.0
+
+### Changed
+
+  * Is now set up to overwrite an old version on import. See “Updating” 
+  instructions in the README.
 
 ### Fixed
 
@@ -53,6 +85,20 @@ When the Seals IRC becomes a thing, I’ll reintroduce this profile, based on th
 then-current version of RatAttack. That’s less work than trying to get current 
 SealAttack up to date
 
+## SpanshAttack 6.0
+
+### Changed
+
+* Is now set up to overwrite an old version on import. See “Updating” 
+instructions in the README.
+
+## StreamAttack 1.0
+
+### Changed
+
+* Is now set up to overwrite an old version on import. See “Updating” 
+instructions in the README.
+
 -----
 
 # 2.0.1 (2020-07-21)

README.md

@@ -129,26 +129,24 @@ likely just ignore them.
 
 ## Updating ##
 
-Sadly VoiceAttack doesn’t let you overwrite an existing profile when you import 
+To make sure that a new version of the profiles actually replaces the old one, 
-a different (newer) version of it. So you’ll have to follow these steps:
+you can’t simply import them again. That would import them as additional copies 
+(“\<profile\>-1”).
 
-1. Look at the release page and see which profiles have been updated (they’ll 
+Instead you’ll have to drop the profile package into the `\Apps\Import` 
-   also be attached as single `.vap` files to the release)
+subfolder of your VoiceAttack installation directory and re-start VoiceAttack. 
-1. Delete these profiles from your VoiceAttack.
+It will prompt you to import the profile package. I have added an “open 
-1. Import the updated profiles.
+voiceattack import folder” command to all profiles for your convenience!
-1. Fix all profiles that include the updated profiles. You are going to have to 
-   re-add the includes (“Edit Profile” → “Options” → “Include commands from 
-   other profiles”).
 
-You could also delete _all_ the profiles, then re-import the entire release 
+**Note**: This will make VoiceAttack run with admin privileges. If you do not 
-package (the `.vax` file). You will still have to fix the includes.
+usually run VoiceAttack with admin privileges, do _not_ have it start 
-
+VoiceAttack for you after importing the profiles. It will keep running with 
-If you have followed the installation instructions above, you will not lose any 
+elevated privileges. Instead re-start it manually. If you are not sure if you 
-of the changes you have made since they will be in a separate profile. **Do not 
+are running with elevated privileges check the “VoiceAttack Information” thing 
-delete** that profile!
+mentioned above. It will include a line about it if it does.
 
 If you delete anything by accident or something didn’t work out quite like you 
-intended, you can find backups of VoiceAttacks data file in 
+intended, you can find backups of VoiceAttack’s data file in 
 `%AppData%\VoiceAttack\Backup`. They get saved every time you change settings or 
 profiles. To restore, close VoiceAttack, find the file with the right timestamp 
 just before you made the changes, copy it to the parent directory, remove the