-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which Windows installer is recommended? #374
Comments
Thanks for raising this @velle, I was looking at the page right now and had similar thoughts. Some more notes:
Stating the obvious / self-evident, I think this sentence could be removed without losing value.
Is already "advanced" information, should go below the download links I think we should have one "main" download link which will be more prominent, so anyone without specific needs clicks on it. This can be latest LTR, with a smallprint below as suggested by @velle . It would be good to also have a "title" for that, so we can explicitly refer to it elsewhere (see #522 (comment)), e.g. "Standalone QGIS long term version installer". And then we can have two more links for "Standalone QGIS latest version installer" and "OSGeo4W Package Manager" (or network installer or whatever, as long as it's consistent :-) ) @timlinux do you have any thoughts / comments on this? |
Information by @agiudiceandrea there was a terminology before, maybe we can recover it. At least partially (and only the terminology and not the complete page :-) ) |
The OSGeo4W installer is what I recommend. The MSIs is just for people who prefer standalone installers or require MSIs for some reason (and in turn have to download a huge blob containing a relatively small new QGIS with mostly unchanged set of dependencies on each update. But they are also handy if you for some reason need an older version. |
I found this https://gis.stackexchange.com/questions/455371/difference-between-qgis-download-and-osgeow4-network-installer.
Is that really how the MSI installers work? If so, isnt that different from how installers normally work and what users would expect? |
See also the edits I proposed here: #522 (comment)
👍🏽
In #522 (comment) I proposed to change the intro text to this: This page provides binary packages (installers) for QGIS. For the actual download section we could then organise it like this: Online installer: [ OSGeo4W Network Installer ] This installer is the best way to keep QGIS up to date, run multiple versions on your system and keep the load on our download servers to a minimum. Using this installer, you can fetch updates to QGIS efficiently since it only downloads the changed sub packages. The installer provides an interactive menu where you can choose which components you wish to install, including special drivers like ECW support etc. During the installation process, you can choose whether you want the Long Term Release (LTR) version or the latest version of QGIS (or both). We recommend the LTR version as it has undergone more quality assurance than the Latest Version. The latter is a good choice if you need the newest features and are not as concerned about stability. Offline installers: [ Long Term Version for Windows (3.34 LTR) ] These installers are for users who wish to easily share the download e.g. putting it on a USB key or network share. The QGIS application and its component libraries need to be completely downloaded each time there is a new release that you want to upgrade to. We recommend the LTR version as it has undergone more quality assurance than the Latest Version. The latter is a good choice if you need the newest features and are not as concerned about stability. |
@timlinux Regarding the way you divided it into "Online installer" and "Offline installers". It is possible to use OSGeo4W to do offline installations; and if I understand correctly it is often the best choice for doing so (see https://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall). How about just "OSGeo4W Installer" and "MSI Installers". |
I have realized that these two pages are very closely related: To avoid too much redundancy, would it be possible to keep the text on the Download page at a bare minimum, maybe 1-2 for each of the three options, and then refer to the Installation Guide for more information? And then perhaps we should have a look at the Installation Guide page, and see if the discussions / suggestions from this thread can be used there instead. |
Hi. Thanks for your message. Yes I am aware of the possibility to use the OSGEO4W installer offline but I think it is good to cater for 'mainstream' use cases. The terms OSGEO4W Installer and MSI installer are language that is not very accessible to every day users, and so I would prefer it if we used simple, clear language as much as possible. |
The term "Standalone installer" (and "OSGeo4W installer") is also currently used in the page at https://www.qgis.org/resources/installation-guide/#standalone-installers |
URL
https://qgis.org/download/
Type(s) of Problems
Other
Summary
What is a "regular user"?
From https://qgis.org/download/, under "Download for Windows".
Please note that English is not my native language.
So what is a "regular user"? Initially I thought it meant a "normal" or "typical" user. But if so, the text suggests basically everyone to download the OSGeo4W installer, right? At least I don't see who should download any of the other installers?
It took me a few minutes to realize that perhaps "regular" means someone who uses it regularly? Is that what is meant?
If I have understood the intention right, then "regular" is not the right term to be used here. Even someone who regularly uses QGIS is not necessarily someone who will need to run various versions in parallel or who will have the super user-ish skills to use the OSGeo4 installer.
OSGeo4W installer vs OSGeo4W network installer
The text refers to "OSGeo4W installer" but the download button reads "OSGeo4W network installer". Is that the same thing? I think so.
My suggestion
Something along the text below.
The text was updated successfully, but these errors were encountered: