Dave,
Michael is correct -- this issue should be fixed.
But, I have an easier way for you to deal with this in the future...
I am not interested in installing multiple versions on my computer. (I know
Michael has to because he has to test Hamlib.)
On my computer, I install WSJT-X in this folder regardless of version:
C:\Program Files\WSJT-X
To do that, you must override the default path offered by the program. This
will leave you with one version. Also, I do not allow the program to add a new
shortcut every time an update is installed. Instead, I have one shortcut on my
desktop to the above path.
Unfortunately, this will still leave you with multiple versions listed in the
Add/Remove Apps control panel. To clean that up:
[1] change the above path temporarily to something else such as:
C:\Program Files\WSJT-Xxxxxxxx
[2] go to the Add/Remove Apps control panel.
[3] uninstall each of the older versions of WSJT-X listed there.
Each time you ask Windows to uninstall, it will say something like
"I can't find that. Would you it removed from the list of programs."
You say yes.
[4] When you are done with step 3, leaving only the most recent version of
WSJT-X showing, undo the name change you made in step 1.
Yes, it's a pain in the neck. But it is a lot faster than what you were doing.
David, AK2L
-----Original Message-----
From: Black Michael via wsjt-devel <[email protected]>
Sent: Monday, January 10, 2022 06:26
To: wsjt-devel <[email protected]>
Cc: Black Michael <[email protected]>
Subject: Re: [wsjt-devel] Cleaner Updates/Installs
This is a long-standing problem that needs to be fixed.
WSJT-X should use a default path that includes the version#.
That will provide two things
#1 Very easy for user to start whichever version they want
#2 Avoid duplicate program entries
This patch makes the default install directory match the WSJT-X version.
diff --git a/CMakeCPackOptions.cmake.in b/CMakeCPackOptions.cmake.in index
eceae4edf..ae1c70900 100644
--- a/CMakeCPackOptions.cmake.in
+++ b/CMakeCPackOptions.cmake.in
@@ -5,7 +5,8 @@
set (CPACK_PACKAGE_VENDOR "@PROJECT_VENDOR@")
set (CPACK_PACKAGE_CONTACT "@PROJECT_CONTACT@")
set (CPACK_RESOURCE_FILE_LICENSE "@PROJECT_SOURCE_DIR@/COPYING") -set
(CPACK_PACKAGE_INSTALL_DIRECTORY ${CPACK_PACKAGE_NAME})
+#set (CPACK_PACKAGE_INSTALL_DIRECTORY
+${CPACK_PACKAGE_NAME}$NAME{CPACK_PACKAGE_VERSION_PATCH})
+set (CPACK_PACKAGE_INSTALL_DIRECTORY
+"@CPACK_PACKAGE_NAME@-PACK_PACKAGE_VERSION_MAJOR@.@CPACK_PACKAGE_VERSIO
+N_MINOR@.@CPACK_PACKAGE_VERSION_PATCH@")
set (CPACK_PACKAGE_EXECUTABLES wsjtx "@PROJECT_NAME@")
set (CPACK_CREATE_DESKTOP_LINKS wsjtx)
set (CPACK_STRIP_FILES TRUE)
Mike W9MDB
On Monday, January 10, 2022, 12:57:41 AM CST, Dave Fitches via wsjt-devel
<[email protected]> wrote:
Hi folks,
Firstly - awesome work with the program to everyone involved (past and
present!)
Just one nit-picky thing...
When we have a new version come out, and I install it, it creates a brand new
Start Menu folder for the new version.
So I now have in my Start Menu:
wsjtx 2.40
wsjtx 2.50
wsjtx 2.52
wsjtx 2.54
Likewise in my installed programs listing in "Add/Remove Programs" I have all 4
versions of the software listed. And given the program installs to the same
location every time it installs, if I remove the old versions of the software,
it causes no end of problems.
To remove the old versions I have to remove the oldest. Then because all the
files are gone, to remove the next oldest I have to re-install the new version.
THEN remove the next oldest. ...rinse and repeat.
To my mind - it should be working thus:
* If you're installing over an existing version in the SAME INSTALL DIRECTORY
(Default behaviour), then it should update the existing package and update the
version number in the Installed Programs list to prevent duplicate listings of
the same install location, and either use a Common Name for the Start Menu
folder, or remove the OLD Start Menu folder for the previous version number and
add the NEW version into Start Menu.
* If you're installing to a brand new directory and there's an existing copy
installed elsewhere, leave the existing stuff alone because some people might
want to run an old version and a new version, so list them seperately.
I admit - I have ZERO programming chops to do any of these things myself, but I
can make constructive suggestions for future releases!
Again - I wish to say I am in awe of the software as it stands! These points
above are piddling things, especially when compared to the joy this program
brings to a new Ham Operator working off a compromised antenna using QRP, and
is still able to make DX contacts despite that! If there was a "Donate here to
support this software" link - I'd be doing it!
Thanks and 73
de VK3DVF
--
= Dave 'Rusti' Fitches =
________________________________________________________
,--__|\ Dave 'Rusti' Fitches
/ \ VK3DVF
\_,--\_x/ * Mobile : +61-419-466-744
v * E-mail : [email protected]
Melbourne, Victoria, Australia
_______________________________________________________
Please Note: Unless this e-mail has been sent as PRIVATE, PERSONAL or
CONFIDENTIAL, the receiver may forward copies of it on the condition that they
send an advisory message to the original sender.
If however the message has been marked PRIVATE, PERSONAL or CONFIDENTIAL prior
consent MUST be obtained before the message can be forwarded.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
