Homebrew version is outdated about xdg-ninja HOT 5 OPEN

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.

from xdg-ninja.

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

from xdg-ninja.

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".

from xdg-ninja.

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.

from xdg-ninja.

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.

from xdg-ninja.