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

Homebrew version is outdated #204

Open
realitymolder opened this issue Dec 8, 2022 · 5 comments
Open

Homebrew version is outdated #204

realitymolder opened this issue Dec 8, 2022 · 5 comments

Comments

@realitymolder
Copy link
Contributor

Hey, seems like the brew version of the program isn't updated, at least since May. (maybe even longer)

@b3nj5m1n
Copy link
Owner

b3nj5m1n commented Dec 8, 2022

I'm not really familiar with brew, but it seems like the package is pinned to the v0.2.0.1 tag, which is unfortunate since the tags are really meant more for the haskell program than the script.

If you know more about homebrew and could help with this, here is the PR which originally added xdg-ninja to homebrew: Homebrew/homebrew-core#104762.

@realitymolder
Copy link
Contributor Author

I'm not really familiar with brew, but it seems like the package is pinned to the v0.2.0.1 tag, which is unfortunate since the tags are really meant more for the haskell program than the script.

If you know more about homebrew and could help with this, here is the PR which originally added xdg-ninja to homebrew: Homebrew/homebrew-core#104762.

Ok, so I did some research, it seems like the progress is manual.
It is mostly dependent on releasing a new binary, but I see that it hasn't been made since May.
So I will suggest 2 solutions:

  1. Release a binary in the repo "release page" every month, a new version with the newest binaries. This will then be updated manually in the brew formula.
  2. Add a function to update the script / JSON database from the script itself - after it has been made, update the Homebrew version "for the last time".

@arcuru
Copy link

arcuru commented Dec 10, 2022

The version in nixpkgs also uses the release tags fyi.

These package managers will always be pinned to something, so when there are releases that's generally what they will use. From the package manager's perspective it is a lot easier if a project has occasional releases but they are usually able to just pin to random git commits if necessary.

@b3nj5m1n
Copy link
Owner

but they are usually able to just pin to random git commits if necessary.

At least for nix that's the case, and I think that's probably the best way to go in this case, since it doesn't really make sense to create a release for every program added, and I'm not sure what else to base it on, except for maybe periodical releases every few months.

@KaBankz
Copy link
Contributor

KaBankz commented Apr 7, 2023

You can always install using the --HEAD flag to install from the latest commit.

brew install xdg-ninja --HEAD

Then upgrade using the --fetch-HEAD flag (only works if you installed from HEAD)

brew upgrade xdg-ninja --fetch-HEAD

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

No branches or pull requests

4 participants