On 02/05/2015 02:39 PM, Matt Wilkie wrote: > Hi Folks, > > A discussion started off-list about a portable Osgeo4W (here > <https://github.com/maphew/apt/issues/10#issuecomment-73048724>). > > Jurgen observed that *"most of the batch files are "portable", but we also > have configuration file templates* that are modified in postinstall using > textreplace. That's essentially why it exists. * > > *BTW another problem with portability are the msvcrt packages - that need > to be installed." *[ *c.f. the batch shell template > <http://trac.osgeo.org/osgeo4w/wiki/PackagingInstructions#Applicationbatchfiletemplate> > ] > I've used o4w portably for a long time by simply copying C:\Osgeo4W tree to > a usb stick and I've not run into problems, but I mostly use just the gdal > command line utils. I thought it would be good to collect and/or itemize > the particular packages or configurations that break portability. We could > then look and see if it's unavoidable or there might be some reasonably > inexpensive way of changing that. > > This this thread; what doesn't work portably right now? > > Matt >
You should talk to J. Cook this is extremely similar to http://www.archaeogeek.com/blog/2014/01/20/portable-gis-v4/ Thanks, Alex _______________________________________________ osgeo4w-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
