Lucas Bremgartner

> I guess we can implement this in several steps > > * Score better archive files based on OS and Arch and don't prompt the user if we have...

> > I don't think we can expect all repos to play nice and include both the OS and the arch in asset names or binary names within archive assets....

I did a quick test with my ~50 binaries managed with bin. For a little bit more than 1/3, I found a `.goreleaser.yml`.

Just for reference, this site lists the valid combinations of arch/os supported by the Go compiler: https://gist.github.com/asukakenji/f15ba7e588ac42795f421b48b8aede63

I like the separation of config and bin-database, because it really feels like two different things.

I would like to have the option on a per-binary base to opt-in for pre releases. E.g. something like this: `bin install --allow-pre-releases github.com/bufbuild/buf`. The default would be `false` and...

I understand. But so far we do not yet have a way in the cli API to distinguish between different flags for different providers. So what is your idea to...

> > But with these packages I currently suffer from the same problem as with the direct installation of binaries, that is, I don't have an easy way of tracking...

Here some additional examples I currently install by using the deb packages and that I would like to have an easy way of keeping track of updates: * https://github.com/rclone/rclone/releases *...

> I have some ideas / questions that it'd be nice to discuss before moving forward with that I am happy to discuss this. > Q: How do we add...