Bug#722450: RFS: osmctools/0.1-1 [ITP] -- Some tools to manipulate OpenStreetMap files
Pierre Blanc wrote...
> I am looking for a sponsor for my package "osmctools"
Strictly speaking for myself, let me share the ideas that crossed my
mind.
> * Package name : osmctools
> Version : 0.1-1
> Upstream Author : Markus Weber
> * URL : http://gitorious.org/osm-c-tools/
Any reason why you dropped the dashes from the upstream name? I find
it hard to see the "osm" in "osmctools".
> osmctools - Some tools to manipulate OpenStreetMap files
Looking at the description (as found in commit b3812e9c)
| Description: Some tools to manipulate OpenStreetMap files
| Small collection of basic OpenStreetMap tools, include converter, filter and
| updater files.
| It masters fewer functions than the commonly-used Osmosis: for
| example, there is no way to access a database with osmconvert.
| However, the program runs faster and offers a few special functions
| (--all-to-nodes, --complex-ways and --out-statistics).
I guess you wanted to start a new paragraph in the third line of the
extended description. Right now this wouldn't work that way.
But honestly, in my opinion the content of the second paragraph is not
that kind of information I'd put or expect in an extended description.
Instead, a listing of the programs included should make them
detectable by advanced package management tools, read: Give the users
a chance to find your package if they are searching for e.g.
"osmconvert".
So, here's how I'd do it:
---------------------------------------------------------------------
Description: Some tools to manipulate OpenStreetMap files
Small collection of basic OpenStreetMap tools, include converter,
filter and updater files.
.
Programs included:
osmconvert - Converter of OSM files
osmfilter - The experimental OSM filters data
osmupdate - Update OSM files
---------------------------------------------------------------------
This will put extra work onto you every time upstream changes the
collection of programs. I think it's worth it.
Regards,
Christoph
Reply to: