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

Binary name conflict #53

Open
drws opened this issue Jul 27, 2023 · 3 comments
Open

Binary name conflict #53

drws opened this issue Jul 27, 2023 · 3 comments

Comments

@drws
Copy link

drws commented Jul 27, 2023

The binary name scan is a very generic one, already-present in many different packages. There are conflicts. Please choose a less-generic global binary name than a simple scan. User can still have a local alias scan if that's preferred.

@rocketraman
Copy link
Owner

Fair enough. Naming suggestions?

@drws
Copy link
Author

drws commented Aug 17, 2023

It's probably best to include a part of the package name. The SANE prefix doesn't seem too important since it's the most used scanning framework, but PDF suffix is more descriptive - so scan-pdf. Still a bit generic, but it seems you're lucky and there aren't any serious conflicts to be found (please double-check). If that's true you could also think about changing the package name to scan-pdf, resulting in a shorter name and no difference between package vs. binary names.

@rocketraman
Copy link
Owner

Maybe I'll add "cli" in there as well as that is a differentiator to other packages that scan to PDF.

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