[GRASS-dev] [GRASS GIS] #2755: Commandline switch "/S" is not working anymore
GRASS GIS
trac at osgeo.org
Tue Jan 12 05:17:26 PST 2016
#2755: Commandline switch "/S" is not working anymore
---------------------------+-------------------------
Reporter: derseppel | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.3
Component: Installation | Version: 7.0.1
Resolution: | Keywords: wingrass
CPU: Unspecified | Platform: MSWindows 7
---------------------------+-------------------------
Comment (by hellik):
Replying to [comment:7 derseppel]:
> Replying to [comment:6 neteler]:
> > Replying to [comment:4 DerSeppel]:
> > > Will it will be fixed in Version 7.0.3 or is it deferred again?
> >
> > Would you want /S to automatically install these (needed) MS Visual
C++ Packages or to skip them?
>
> Depends on how this will be implemented.
>
> If it checks which versions are already installed and then just installs
the missing versions, it would be nice.
>
> But for me it will also be Ok if all VC++ installations are skipped when
the needed versions are documented somewhere easy to find.
the reason why the windows pops up is that some time ago it was changed to
install the runtimes by default.
AFAIR background: there were many complaints in the ML that winGRASS isn't
working caused by missing runtimes; therefore the install by default. the
runtimes can't be deployed by winGRASS itself cause of licensing issues;
therefore the explicit popup window informing.
have a randomly look e.g. at:
http://stackoverflow.com/questions/12206314/detect-if-visual-c
-redistributable-for-visual-studio-2012-is-installed
there is no easy way to determine/identify which MS runtime versions are
already installed, complicated by 32bit and 64 bit and so much different
runtime versions (SP, etc etc).
some possibilities to solve this ticket:
- find an easy way to implement how to check already installed MS runtimes
versions and compare it with the needed ones and install it case by case
(input/code/... very welcome!)
- change the installer back to previous status (without installing MS
runtimes by default); possible sideeffect: new complaints of users tha
winGRASS isn't working (see above)
I tend to ''wontfix'' for this ticket.
any opinions?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2755#comment:8>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list