Package Details: bazelisk-bin 1.19.0-1

Git Clone URL: (read-only, click to copy)
Package Base: bazelisk-bin
Description: A user-friendly launcher for Bazel
Upstream URL:
Keywords: bazel bazelisk build skylark starlark
Licenses: Apache
Conflicts: bazel, bazelisk
Provides: bazel, bazelisk
Submitter: sudoforge
Maintainer: FantasqueX
Last Packager: FantasqueX
Votes: 4
Popularity: 0.169278
First Submitted: 2020-02-07 10:55 (UTC)
Last Updated: 2023-11-17 06:07 (UTC)

Dependencies (0)

Required by (68)

Sources (1)

Pinned Comments

Latest Comments

uhthomas commented on 2023-10-11 13:32 (UTC)

Thanks again for the help and being receptive to feedback!

FantasqueX commented on 2023-10-11 13:31 (UTC)

Maybe in some cases users need bazelisk specifically. Your suggestions are reasonable. Thanks. I have updated the package.

uhthomas commented on 2023-10-11 13:13 (UTC)

Thanks! :) It may also be worth updating the 'provides' section to include 'bazelisk'?

FantasqueX commented on 2023-10-11 02:27 (UTC)

I have readded bazel as provides referring to official brew package. Thanks for your suggestions! @uhthomas

uhthomas commented on 2023-10-11 01:09 (UTC)

I feel like it would be better to install this tool as 'bazel', as is convention in the Bazel community.

Install it as the bazel binary in your PATH (e.g. copy it to /usr/local/bin/bazel). Never worry about upgrading Bazel to the latest version again.

This is also how the official 'setup-bazelisk' GitHub action works.

There has also been discussion of adding both for this package in the past.

FantasqueX commented on 2023-10-10 02:07 (UTC)

Hi! Sorry for breaking changes without prior notice. The README of bazelisk just uses bazelisk instead of bazel. I think this package should only provide bazelisk instead of bazel.

uhthomas commented on 2023-10-09 23:38 (UTC) (edited on 2023-10-09 23:39 (UTC) by uhthomas)

Hi! The new version installs the binary as bazelisk rather than bazel, which is a bit inconvenient and unexpected. Is it possible to revert this behaviour change? I imagine this will also break existing users of the package, and dependencies which depend on 'bazel' as that is what this package is named in the 'provides' section.