Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
das-g opened this issue Jul 5, 2020 · 3 comments
Open

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

das-g opened this issue Jul 5, 2020 · 3 comments

Comments

@das-g
Copy link

das-g commented Jul 5, 2020

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

Package names in nixpkgs:

  • must be lowercase
  • cannot contain spaces
  • may be hyphenated

(See section Package naming in the Nixpkgs manual.)

Given these constraints, what should the package name be?

  • osmexpress?
  • osm-express?
  • osmx, like your PyPI package for the python lib?
@bdon
Copy link
Member

bdon commented Jul 6, 2020

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
Copy link
Author

das-g commented Jul 9, 2020

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
Copy link
Member

bdon commented Jul 10, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants