Skip to content

1.2! The lustful update.

Compare
Choose a tag to compare
@xplshn xplshn released this 20 Feb 14:29
· 263 commits to master since this release
d3b03fa

Yeah yeah, new and all the BS. But, why should I update?

  • Fixed install.go not handling errors correctly
  • Fixed an edge case with run.go where it wouldn't download
  • Fixed "info" not showing anything for programs not described in metadata.json.
  • Fixed fetch_binary in helperFunctions.go | Now it uses Goroutines
  • Made the spinner function from spin.go receive a stop/halt signal.
  • Now you can CTRL+C in all commands (except for remove/del, its too fast for you to stop)
  • Added "fast_info" (Its the old info command, it is faster because it reads only one json file, while the other uses data from difference sources.)
  • Introducing "update", the command will update every binary in your $INSTALL_DIR (if set) OR ~/.local/bin, how? It checks the SHA256 sum of every binary against the repo's metadata. (For now, its pretty basic, it does not receive any argument, it just updates everything.)

Go ahead, try this juicy piece of software -> Help me develop bigdl, feel free to open issues, request features & and ask questions.

Feedback is welcome. Even if it is just to add more idiotic wording to the README.md

Ebigdl? Announcement. Single source file, complete functionality - The hacker's edition ; bigdl in just 1234 lines (1073 loc).

Ebigdl is the result of concatenating every .go file into a single .go file and removing the unnecessary imports. I am working in making bigdl and ebigdl completely modular, meaning you could simply remove the files corresponding to functionality you don't need... Pretty cool, huh?

As usual, if you want to test it without installing, here's a one-liner.

curl -qfsL "https://github.com/xplshn/bigdl/releases/download/1.2!/bigdl_amd64" -o bigdl_amd64 && \
 chmod +x bigdl_amd64 ; \
  command -v ./bigdl_amd64 && \
   ./bigdl_amd64 run --silent gum confirm "Do you want to test $PWD/bigdl_amd64?" --negative="No, remove it!" || \
     rm ./bigdl_amd64 ; \
   command -v ./bigdl_amd64 && \
    X=$(./bigdl_amd64 run --silent gum input --placeholder="Usage: bigdl [-vh] {list|install|remove|update|run|info|fast_info|search|tldr} [args...]") && \
     echo "$X" | awk '{ for (i = 1; i <= NF; i++) { if ($i ~ /^(--help|--version|-v|-h|list|install|remove|update|run|info|fast_info|search|tldr)$/) { for (j = i; j <= NF; j++) { printf "%s ", $j }; print ""; break } } }' | \
      xargs -r ./bigdl_amd64
Why the idiotic wording? I am not good at writing readmes, so, I asked cgpt to write a readme for a program, and I told it to make a "sexy readme" so, cgpt basically started the tradition.