[osgeo4w-dev] [osgeo4w] #713: --advanced command line flag doesn't work

[OSGeo4W]

#713: --advanced command line flag doesn't work
-----------------------+----------------------------
Reporter:  tdanckaert  |       Owner:  osgeo4w-dev@…
    Type:  defect      |      Status:  new
Priority:  major       |   Component:  Installer
 Version:              |  Resolution:
Keywords:              |
-----------------------+----------------------------
Comment (by monstermushroom):

 What I see is that in my .bat script, in an environment where I first
 delete the INSTALL_ROOT before the first command:



 %STAGE_ROOT%\osgeo4w-setup-x86_64.exe  --advanced --arch x86_64
 --autoaccept --delete-orphans --no-desktop -l %STAGE_ROOT%\osgeo64_install
 --site "http://download.osgeo.org/osgeo4w/v2"  --upgrade-also --packages
 gdal --root %INSTALL_ROOT% -q

 %STAGE_ROOT%\osgeo4w-setup-x86_64.exe --arch x86_64  --autoaccept
 --delete-orphans --no-desktop -l %STAGE_ROOT%\osgeo64_install --site
 "http://download.osgeo.org/osgeo4w/v2"  --upgrade-also --packages proj
 --root %INSTALL_ROOT% -q



 The first command to install gdal does a successful silent install in
 advanced mode as expected.  This is running a fresh install.


 In the second command, installing proj in the existing INSTALL ROOT, I
 have the bug described above.  If I run the command with the --advanced
 flag, then it opens an Express Window (with GDAL checked) instead.  If I
 take the --advanced flag away, the proj installation works in advanced
 mode.


 So I think the problem described above is something that happens when the
 install directory already exists.  I think if @tdanckaert deletes their
 install directory before running, they  will find that the --advanced flag
 is working.
-- 
Ticket URL: <https://trac.osgeo.org/osgeo4w/ticket/713#comment:1>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.