Adding pack CLI

[kdavis586]

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 your PR looks excellent! 🚀

[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/pack/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/pack/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/18550527467. Examine the logs at this URL for more detail.}

[kdavis586]

@conda-forge/help-go ready for review! (First contribution. Tried my best to reference the docs)

[kdavis586]

I've pinged you (the go team) because the pack CLI is built with go, but I've used the built binaries from the releases section in the meta.yml

[kdavis586]

@conda-forge/core any guidance would be greatly appreciated!

Explanation for why I originally marked the PR as golang above

[mfansler]

Thanks for submitting! ❤️

In current form, this doesn't follow typical practice, so I suggest revising.

---

BTW, conda-forge/staged-recipes is the broader team to escalate to if a language-specific team is unresponsive (usually give teams 72 hours between pings/reaching out to others). They is also the Zulip forum that can be more responsive. The conda-forge/core team is often fully occupied with infrastructure and governance issues, so they're unlikely to respond to activity here.

[mfansler]

Typically, redistributing binaries is not accepted here without explanation. Perhaps it would be helpful to consult previously merged recipes with the go label for reference.

Looking at upstream's GitHub workflow build.yml, they use make to do the builds. So, switching to the source tarball and using make build might be a good place to start.