Add recipe for hyphen

[haecker-felix]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

• recipes/hyphen/recipe.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: Hofer-Julian. Please ask them to comment on this PR if they are.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/hyphen/recipe.yaml) and found it was in an excellent condition.

[Hofer-Julian]

I am willing to maintain this package

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[haecker-felix]

Source is from official source.

Not sure how to deal with this, as the upstream source for tarballs is sourceforge:

https://sourceforge.net/projects/hunspell/

Currently pointing to a sourceforge mirror (https://netcologne.dl.sourceforge.net)

[haecker-felix]

@conda-forge-admin, please ping team @conda-forge/help-c-cpp

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[wolfv]

We actually don't run osx + arm64 configuration in the staged recipes so this could be removed for now.

Also, if the config.sub needs updating, we might be able to use this from https://conda-forge.org/blog/2020/10/29/macos-arm64/#how-to-add-a-osx-arm64-build-to-a-feedstock

For autotools package, add the following to recipe/meta.yaml,

requirements:
  build:
    - gnuconfig   # [unix]

and to recipe/build.sh,

# Get an updated config.sub and config.guess
cp $BUILD_PREFIX/share/gnuconfig/config.* .

[haecker-felix]

Dropped osx + arm64

[wolfv]

looks good overall!