Skip to content

Conversation

@zeroshade
Copy link
Member

closes #85

@zeroshade
Copy link
Member Author

I haven't created columnar-tech/homebrew-dbc yet. I'll do so once we're clear on this PR

Copy link
Member

@amoeba amoeba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Looks about right to me. Left two notes.

.goreleaser.yaml Outdated
Comment on lines 294 to 296
- dbc@{{ .Version }}
- dbc@{{ .Major }}
- dbc@{{ .Major }}.{{ .Minor }}
Copy link
Member

@amoeba amoeba Oct 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- dbc@{{ .Version }}
- dbc@{{ .Major }}
- dbc@{{ .Major }}.{{ .Minor }}
- dbc@{{ .Version }}
- dbc@{{ .Major }}.{{ .Minor }}

I think we could totally skip this but at least I don't think we need all three aliases. What do you think about just Major.Minor for now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at a minimum we should do Version + Major/Minor

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edited my suggestion.

.goreleaser.yaml Outdated
description: "A CLI utility for managing ADBC drivers"
repository:
owner: "columnar-tech"
name: "homebrew-dbc"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
name: "homebrew-dbc"
name: "homebrew-tap"

It's slightly more conventional to call the repo "homebrew-tap". That carries the benefit of us not having to rename the repo if we create more formulae/casks.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it? Everything I was seeing was that it should be homebrew-${package} I thought? Though I guess you're right for the case where we might want to create more under the Columnar org...

@ianmcook thoughts?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea, but if the docs say to use homebrew-tap then that seems like a good reason to.

@ianmcook
Copy link
Member

Thanks for doing this!

@zeroshade
Copy link
Member Author

I created columnar-tech/homebrew-tap and a PAT for the workflow to use.

@zeroshade zeroshade merged commit f15fa8c into main Oct 21, 2025
13 of 14 checks passed
@zeroshade zeroshade deleted the homebrew-tap branch October 21, 2025 16:56
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 this pull request may close these issues.

Support Homebrew installation for dbc

4 participants