As noted in #177 homebrew has certain "notability threshold" requirements before they will accept new formulae into their main "tap" (package repository).
Setting up and maintaining a third-party tap is easy though, and many homebrew users are familiar with using them; it's easy for us to document how users can install from our tap as well.
Having a single tap for the asdf-format organization would be useful, as we can use it for libasdf, libasdf-gwcs, and anything else we deem useful to ship via homebrew.
We could also consider a custom conda channel, though I think this is less necessary since conda-forge is already pretty lenient in what it will accept so long as a package has dedicated maintainers.
Ref: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap
@braingram could you please add a repository called "homebrew-tap"? That naming scheme allows users to run brew tap asdf-format/tap which is the common idiom.
As noted in #177 homebrew has certain "notability threshold" requirements before they will accept new formulae into their main "tap" (package repository).
Setting up and maintaining a third-party tap is easy though, and many homebrew users are familiar with using them; it's easy for us to document how users can install from our tap as well.
Having a single tap for the asdf-format organization would be useful, as we can use it for libasdf, libasdf-gwcs, and anything else we deem useful to ship via homebrew.
We could also consider a custom conda channel, though I think this is less necessary since conda-forge is already pretty lenient in what it will accept so long as a package has dedicated maintainers.
Ref: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap
@braingram could you please add a repository called "homebrew-tap"? That naming scheme allows users to run
brew tap asdf-format/tapwhich is the common idiom.