Open Losty17 opened 3 months ago
Hi.
An install script could be a nice addition, but I'd like to change some things:
~/.local/lib
and link in ~/.local/bin
instead of ~/.config
(which is supposed to be used for config files of installed programs)git clone
instead of curl
so people can git pull
to get updates&&
(generally, one line should do only one thing). People can paste multiple lines in the terminal if they want..zshrc
or .bashrc
(or both). This is intrusive behaviour, and the decision should be left to the user how they want to invoke cutefetch
. We can make suggestions in the documentation, but that's it.I propose appending the following to the Install
section:
cutefetch
mkdir -p ~/.local/lib
mkdir -p ~/.local/bin
git clone https://github.com/cybardev/cutefetch ~/.local/lib/cutefetch
chmod a+x ~/.local/lib/cutefetch/cutefetch
ln -s $HOME/.local/lib/cutefetch/cutefetch $HOME/.local/bin/cutefetch
PS1: after running the above commands, make sure to add the bin directory to path or add an alias to cutefetch so it can be run from the terminal. Put one of these in your shell script config file (.bashrc
, .zshrc
, etc.):
Add the local bin directory to PATH:
export PATH="$HOME/.local/bin:$PATH"
Add an alias to your shell script config file:
alias cutefetch="~/.local/bin/cutefetch"
PS2: On many distros, the local bin directory is already added to PATH. After running the installation commands, check if you can run cutefetch
already (in a new terminal, not the current one). If you can, then you don't need to do anything else.
You can add the changes and make a PR. I'll check it when I can get to it. Thanks. :blush:
Description
In the purpose of easing the process of installation, I have made a single line bash script to download the script, place it in a file and add it to PATH. I offer myself to update the README.md if necessary.
Changes Requested
Resources
sectionResources