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

bin/analyze is too generic as a name #596

Open
1 of 3 tasks
bsiegert opened this issue Oct 21, 2018 · 0 comments · May be fixed by #605
Open
1 of 3 tasks

bin/analyze is too generic as a name #596

bsiegert opened this issue Oct 21, 2018 · 0 comments · May be fixed by #605

Comments

@bsiegert
Copy link

The issues can be of three types (put an X between the brackets):

  • Bug reports
  • Change request or feature request
  • Others, questions

I am one of the developers of pkgsrc, a package collection. In hunspell, src/tools/Makefile.am contains:

bin_PROGRAMS=analyze chmorph hunspell munch unmunch hzip hunzip

This will install the named binaries into $PREFIX/bin. However, at least "analyze" is way too generic. analyze does not seem to be needed if you just install hunspell as a dependency of, say, libreoffice, and there are other packages (such as go-tools) that try to install a binary named "analyze".

  • Could analyze be renamed to, for example, hunspell-analyze? (A similar consideration applies for munch and unmunch, by the way.)
  • Or perhaps the tools could be installed into $PREFIX/libexec/hunspell by default?
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

Successfully merging a pull request may close this issue.

1 participant