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

feat: create kubo recipe in homebrew #9449

Closed
3 of 5 tasks
SgtPooki opened this issue Dec 2, 2022 · 1 comment
Closed
3 of 5 tasks

feat: create kubo recipe in homebrew #9449

SgtPooki opened this issue Dec 2, 2022 · 1 comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Dec 2, 2022

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

We should create a new recipe in brew.sh for kubo. Currently, it's still using old ipfs namespace.

Open questions:

  • Should we keep publishing ipfs recipe and publish an additional kubo recipe?
  • Can we create an alias from a new kubo recipe to the original ipfs recipe or vice/versa?

Related

@SgtPooki SgtPooki added the kind/enhancement A net-new feature or improvement to an existing feature label Dec 2, 2022
@lidel
Copy link
Member

lidel commented Dec 6, 2022

Kubo project only maintains official Docker images at https://hub.docker.com/r/ipfs/kubo/ and signed binaries at https://dist.ipfs.tech/#kubo

Everything else is maintained by community – so out of scope, and i am closing this, but feel free to open PR against brew if you use homebrew :-)

ps. note other package managers already renamed, without Kubo team's involvement, for example:

@lidel lidel closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants