> > Regardless, there are other ways of approaching this issue, for example, > > the openstreetmap-carto package could produce two binary packages, the > > first containing the style.xml file, and the second which depends on the > > first, and handles copying it and editing it for the user. In this > > scenario, you could just depend on the first package, and avoid any > > questions being asked of the user. > > This is a very good idea. It will provide full flexibility. All the > reusable things should be in a separate package called > openstreetmap-carto-common or something similar (or perhaps > openstreetmap-carto vs openstreetmap-carto-config). Then users who > just want an OSM tile server up running can just install > osm-tile-server which pulls in -common, while the more advanced user > can install openstreetmap-carto and configure every detail > individually.
I've split it into two packages and put it on a branch: git clone git://anonscm.debian.org/pkg-grass/openstreetmap-carto.git -b two_packages Ruben
