cmdLookup - Stardance

30m 37s logged

This project got denied so many times for bogus reasons, and now I’m forced to devlog to resubmit apparently. THEY TOLD ME I NEEDED SOURCE CODE IN MY REPO, WHEN I LITERALLY HAVE SOURCE CODE IN MY REPO. ITS THE FRICKIN BASH SCRIPT.

Ship #1 Pending review

@Pixeleyesd on cmdLookup · 25 days ago

I made a Linux commandline tool that allows you to check the use and install commands of a tool / program. This is incredibly useful when installing certain apps, so you don't need to google the install script of any command, which is a common problem I have. It uses APIs and local information.

Major QoL improvements:

- You can find the install location of any program you enter
- You can see the installation command of any program entered
- You can see the help menu of any program entered

Minor QoL improvements:

- You can easily see the description of any program entered
- You can see what command correlates to any program entered

Syntax is:
cmdlookup [command] [options]

Install script:
apt (Debian and debian based distros):
curl -1sLf '[https://dl.cloudsmith.io/public/pixeleyesd/cmdlookup/setup.deb.sh](https://dl.cloudsmith.io/public/pixeleyesd/cmdlookup/setup.deb.sh)' | sudo -E bash
sudo apt install cmdlookup

dnf (Redhat distros):
curl -1sLf '[https://dl.cloudsmith.io/public/pixeleyesd/cmdlookup/setup.rpm.sh](https://dl.cloudsmith.io/public/pixeleyesd/cmdlookup/setup.rpm.sh)' | sudo -E bash
sudo dnf install cmdlookup

thank you :3

4 devlogs
7h
Frictionless

Try project → See source code →

Open comments for this post

@Pixeleyesd on cmdLookup · 25 days ago

2h 5m 23s logged

The API is now working fully, and aside from some accidental inconsistencies, the project is largely ready to ship!

Open comments for this post

@Pixeleyesd on cmdLookup · 26 days ago

1h 48m 36s logged

I finished setting up my Cloudsmith repository. you can now the package by typing: (https://dl.cloudsmith.io/public/pixeleyesd/cmdlookup/setup.deb.sh)’ | sudo -E bash then type: sudo apt install cmdlookup. I also made the package name and the command name behave the same when inputted, and also made invalid values show up as “Invalid”

Open comments for this post

@Pixeleyesd on cmdLookup · 27 days ago

1h 59m 16s logged

I have the status of whether the program is installed on the PC or not, as well as using the APIs listed before to add the description. I also locally fetch the install location if installed, and I output the help menu of the program if this is the case. Next step is to fetch the help menu or equivalent over an API.

Open comments for this post

@Pixeleyesd on cmdLookup · 28 days ago

1h 12m 10s logged

I started work on my bash script that automatically finds the use of a given command, as well as where to download the package that uses the command.

First, I looked for and found a few APIs I wanted to use for this project. I settled on
https://command-not-found.com
and https://cheat.sh
for my main, and for the backup, in case command-not-found.com goes down, I went with https://packages.debian.org/search?keywords=.

Originally, when you put in, for example, firefox, the code was structured like as follows:
INSTALL_APT=“sudo apt install $COMMAND”
INSTALL_PACMAN=“sudo pacman -S $COMMAND”
INSTALL_DNF=“sudo dnf install $COMMAND”
INSTALL_ZYP=“sudo zypper install $COMMAND”
INSTALL_BREW=“brew install $COMMAND”
INSTALL_SNAP=“sudo snap install $COMMAND”

this basically meant that it would always tell you:

Installation Commands:
Debian/Ubuntu (APT): sudo apt install firefox
Arch Linux (Pacman): sudo pacman -S firefox
Fedora/RedHat (DNF): sudo dnf install firefox
openSUSE (Zypper): sudo zypper install firefox
macOS/Linux (Brew): brew install firefox
Universal (Snap): sudo snap install firefox

which is clearly NOT RIGHT

The solution was to use the APIs (as mentioned before) to look for the methods of installation. I’m now working on getting the local status of packages and displaying that, as well as using local information of the packages BEFORE using the APIs to fetch.