TekWizely here (creator of the linked project) - I didn't create this post but thanks to OP for sharing.

Happy to answer any Qs.

Also, I'm about to add a killer feature that lets each template tag provide a printf specifier to format values beyond the simple '%s' (current default).

Thanks again !

-TekWizely

LOL I know right!

for the record, the project idea came first, and the brainstorming for names came after.

But it was definitely a eureka moment that made me double-excited to create and share the project !

Thanks [for] the comment,

-TW

Greetings! Thanks a lot for taking the time to look at Bingo.

1: re: copy-paste install script: I'll definitely grind on this and see what we can do. Bingo requires my Run[1] package, which itself is written in go and can be installed via `go install github.com/TekWizely/run` -- Additionally, once you have Bingo installed, you can use IT to re-install Run and then manage your Run installation via Bingo itself ! A self-running install script for Bingo that installs a temporary version of Run, then installs Bingo, then uses Bingo to install a permanent version of Run would actually be quite clever !

2: re: metapackages: Bingo's goal is to be a useful wrapper on top of Go's built-in, and highly useful, install feature. Go's auto compile+install features are already getting pretty complex (ie code generation, specifying tags, etc)... The fact that you can download and install hugo with `--tags extended` from the command line is pretty sweet. That said, I would say any additional support (ie metapackages) might first start as a request against go install proper -- That said, it might be a nice addition to maybe fetch some kind of `go.install` file that contains basic steps for installing a complex package. If it was going to be a non-sanctioned idea, I would still want the format of the file/spec to stand on its own and be useful outside of Bingo.

3: re: shell/path setup script: PRs always appreciated ;)

4: Graci ! I am quite pleased with myself for the name - BTW: The idea for the tool came first. I then brainstormed the name ...

Thanks again and please lemme know if you have any further comments/questions! If nothing else please consider opening Issues for these ideas to help me keep track of them :)

-TW

[1]https://github.com/TekWizely/run

Hi!

Bingo is basically a wrapper over `go install` that makes it easier to manage the binary after installation. ABI and Distro etc issues are resolved however Go resolves them internally.

The beauty of Bingo is that it uses Go's built-in project install feature, ie. its as easy as as replacing `go` with `bingo` :

   $ bingo install package-url

you don't need to maintain any package information.

I'm not sure if nix can install (+ manage) golang binaries from the command line using _just_ the package url / binary name?

LOL Actually one my hopeful future additions is to maintain (or use discovery) a list of name-to-repo mappings.

ie. I would love for users to be able to just do:

   $ bingo install hugo
   ... installing github.com/gohugoio/hugo

I don't really want the concept of any project _owning_ a name, so in the cases where multiple projects were mapped/discovered for a given name, we'd want to ask the user which one they wanted to install.

(I was on xmas vacay so missed the initial post)

Wow what a nice random surprise - Thanks OP for the call out!

Go already makes installing go apps extremely easy, ie:

    go install package-url

What Bingo tries to do is make _managing_ that installed binary just as easy.

Once installed, you can then manage the installation by the binary's name.

An example I personally use:

    $ bingo install github.com/gohugoio/hugo
    # ... two versions later
    $ bingo update hugo

I'm happy to try to answer any questions - else I'll be perusing the comments looking for places to chime in.

Thanks again,

-TW

Just a quick drive-by to say thanks for the call-out - I hope you're finding run to be a useful tool and would love to hear more about how you're using it!

Clickable link: https://github.com/TekWizely/pre-commit-golang/releases/tag/...

I see this post has finally devolved into a discussion around using make as a task runner (it hadn't yet when I first read the article yesterday)

With that in mind, I toss my tool into the ring:

Run: Easily manage and invoke small scripts and wrappers - https://github.com/TekWizely/run