[Xastir] New Online Maps in Git (Canada & U.S.)

[David Ranch]

Hey Tom,

> If it's not throwing errors at "make install" time, then I am out of ideas for where to look.

Ok.. that's a good question.  WHERE should those .geo files be 
installed?  What I see is:

$ find /usr/share/xastir | grep geo
--
./scripts/inf2geo.pl
./scripts/ozi2geo.pl
./scripts/geopdf2gtiff.pl
./scripts/mapblast2geo.pl
./maps/Online/OSM_tiled_cycle.geo
./maps/Online/OSM_tiled_fosm.geo
./maps/Online/OSM_tiled_mapnik.geo
./config/OSM_geofabrik_roads.dbfawk
./config/OSM_geofabrik_waterways.dbfawk
--

I don't see the new scripts in the installed 
/usr/share/xastir/maps/Online directory.  Looking at the output of "make 
install", it doesn't look like they are being copied over:
--
. . .
test -z 
"/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/maps" 
|| /bin/mkdir -p 
"/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/maps"
  /usr/bin/install -c -m 644 worldhi.map CC_OpenStreetMap_logo.png 
CC_OpenStreetMap_txt.png 
'/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/maps'
test -z 
"/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/maps/Online" 
|| /bin/mkdir -p 
"/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/maps/Online"
  /usr/bin/install -c -m 644 OSM_tiled_cycle.geo OSM_tiled_mapnik.geo 
OSM_tiled_fosm.geo 
'/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/maps/Online'
test -z 
"/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/sounds" 
|| /bin/mkdir -p 
"/home/dranch/rpmbuild/BUILDROOT/xastir-2.0.9-3.20160809gitb4f6124d.el6.x86_64/usr/share/xastir/sounds"
. . .
--


> With CVS, it is a royal pain to move files around once they're created --- you
> can cvs remove and cvs add them again, but that loses all the history.  So
> there is a strong tendency with CVS not to reorganize files.  It's not the
> case with git, so there's no real impediment to reorganization.

Well.. now that we're in Git.. hopefully this is easy(er).


> Once we figure out why it is that some folks can't get 'em installed, we
> could "git mv" them to a different directory and update the build system
> accordingly.  But let's first figure out what's wrong with the current
> picture.

Good plan!

--David