protomaps / OSMExpress

Fast database file format for OpenStreetMap
BSD 2-Clause "Simplified" License
229 stars 19 forks source link

What's the preferred linux package name for OSM Express? #19

Open das-g opened 4 years ago

das-g commented 4 years ago

Cool project! I'm considering to package OSM Express for NixOS / nixpkgs.

Package names in nixpkgs:

(See section Package naming in the Nixpkgs manual.)

Given these constraints, what should the package name be?

bdon commented 4 years ago

Hmm, my inclination is that osmexpress feels less arcane than just osmx. If we use that, maybe we should change the command line tool name and python package as well?

das-g commented 4 years ago

Hmm, my inclination is that osmexpress feels less arcane than just osmx.

The long forms are more explicit about what the name means, yeah. As you didn't mention the variant with a hyphen, do you prefer osmexpress over osm-express? "osm" already being an abbreviation, I find the latter easier to decipher.

If we use that, maybe we should change the command line tool name and python package as well?

While it's quite common to have command names and package names match (especially with packages that provide exactly one command), command names that deviate from the package name aren't unheard of. Take mercurial, whose main command is hg, or subversion, whose main command is svn. Because a command is usually typed much more often than a package name, brevity can be a valid concern.

I don't know how established the osmx Python package already is. If it's in wide use already, you might wish to keep its name.

bdon commented 4 years ago

python import statements can't have -, so avoiding _ or - seems more flexible in general. I don't believe there are many users of the python package right now, so that shouldn't factor into changing the name.