Am Freitag 24 April 2009 schrieb Hamish:
> Guenther wrote:
> > the poi database is part of gpsdrive, it won't work without.
> > so the geoinfo.db and some icons are required for gpsdrive to run.
>
> ok, as a fall-back can we work on a minimal (dozen?) basic icon set like
> "x" "o" triangle, etc.? probably the old WLAN etc set from gpsdrive 2.09
> would do. hopefully it is very little work, won't need to be maintained,
> and well help out a lot of folks.
>
I also had that idea, that we just provide a small set of base icons.
the problem is, that joerg did the packages, and he currently has other more
important things to do...
I could provide a tar containing the base icons, if that would help.
> don't misunderstand -- I am glad that we now depend on that package
> instead of trying to maintain our own icon set. But I think we need a
> minimal 12-icon starter-pack drop-in replacement option too (probably 20k
> instead of requiring megabytes).
>
I fully understand this :-)
> for now I've symlinked geoinfo.db from an old version of the package and
> as long as I don't try to create any waypoints I'm fine.
>
I had some discussion with joerg, where to put the geoinfo.db.
then we moved it from gpsdrive-data to the openstreetmap-map-icons package.
one of the reasons was, that we hope, that other application can also make use
of it. but I'm not happy with the install location in /usr/share/icons/...
because as it is not an icon file but a database it should stay somewhere
else; even it is directly related to the icons...
> that version switching exposed another problem: it made dpkg very upset
> that the Python-Version was not set and it refused to do anything. In
> the end to get it unstuck I had to temporarily move away
> /usr/bin/pycentral, run dpkg to reinstall, then move pycentral back into
> place. :-/ no fun
>
I never understood the python dependency. afaik python is only used to
prerender mapnik maps, which is not really required for gpsdrive to run...
> Again as Etch can't use Mapnik/OSM, and only python2.4 is available there,
> I don't think we need python at all there so can rip it out in the etch
> patch set.
>
right.
> fwiw, I care to keep 2.10rc1 etch-compatible for a couple reasons:
> - avoid developer monoculture
> - if we can't get it to build on debian(-1), what hope is there for
> the mac osx/fink version etc to work?
> - often the choice of distro is somewhat out of the user's hands, or
> they have important reasons to stay with an older OS that has nothing
> to do with gps.
> - we shouldn't force people into the constant upgrade-mill.
>
I understand that, but I also think, that especially with debian, which has
very long release cycles and the releases are very stable, it is enough to
support the current stable release.
but if you like to do the support for etch, feel free to support it ;-)
_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive