setop
/
cliget
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

more entries in the catalog ; more readme and faq

This commit is contained in:
setop 2023-02-02 11:29:38 +01:00
parent e5a8651e57
commit c456d2d46d
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@ -12,7 +12,7 @@ You have a bunch of useful tools for day to day activity in the terminal, as a d
But you never know if there are up to date, where they come from, what do they to exactly, do you still need them. But you never know if there are up to date, where they come from, what do they to exactly, do you still need them.
Few of them are part of you OS package manager. Most of the time old version. And you may not want to insall them system wide actually. Few of them are part of you OS package manager. Most of the time old version. And you may not want to install them system wide actually.
Cliget lists, installs and updates standalone command line utilities in your user profile. Cliget lists, installs and updates standalone command line utilities in your user profile.
@ -30,7 +30,7 @@ Inspired by envinstall (private), [webinstall](gh:webinstall/webi-installers), [
- [ ] from tar.gz - [ ] from tar.gz
- [ ] exe - [ ] exe
- [ ] wheel (python) - [ ] wheel (python)
- [ ] overriding info from the caralog (repo, version) - [ ] overriding info from the catalog (repo, version)
- [ ] list installed - [ ] list installed
- [ ] identify installed version - [ ] identify installed version
- [ ] can install itself - [ ] can install itself
@ -53,18 +53,18 @@ Inspired by envinstall (private), [webinstall](gh:webinstall/webi-installers), [
#### What does it do, again ? #### What does it do, again ?
CliGet automates the followingi process: CliGet automates the following process:
1. go to my useful tool website 1. go to my useful tool website
1. navigate to release section 1. navigate to release section
1. check if it has been updated 1. check if it has been updated
1. if so, download, extract, install 1. if so, download, extract, install
1. repeat for all the useful small toos I use 1. repeat for all the useful small tools I use
1. repeat periodically 1. repeat periodically
CliGet has nice defaults, favors convention over configuration, and does its best to "guess" how to get current version numner, get last version number, download last release and install it properly. CliGet has nice defaults, favors convention over configuration, and does its best to "guess" how to get current version number, get last version number, download last release and install it properly.
Tools developper / mantainers are not supposed to know CliGet exists. It adapts to the way they deliver thier software. Of course if they use GitHub release and TGZ, it's easier for Cliget to manage :') Tools developers / maintainers are not supposed to know CliGet exists. It adapts to the way they deliver their software. Of course if they use GitHub release and TGZ, it's easier for Cliget to manage :')
#### so I have to do this process for CliGet ? #### so I have to do this process for CliGet ?
@ -72,29 +72,29 @@ Only the first time. After being installed, CliGet is managed by CliGet.
#### I already use [asdf](https://asdf-vm.com/), why would I need cliget ? #### I already use [asdf](https://asdf-vm.com/), why would I need cliget ?
asdf is a wonderful tool when it comes to do software development in various programing language while mixing versions from one project to an other. asdf is a wonderful tool when it comes to do software development in various programming language while mixing versions from one project to an other.
But this power comes with some constraints : a plugin has to be developped in order to integrate a new tool to asdf ; And versions of every tool that will be used for a project has to be declared in a config file. But this power comes with some constraints : a plugin has to be developed in order to integrate a new tool to asdf ; And versions of every tool that will be used for a project has to be declared in a config file.
CliGet does not handle multiversions, tools are deployed for your whole profile. CliGet does not handle multi-versions, tools are deployed for your whole profile.
In short, if you want to manage development environment, use asfd. If you want to install small tools, use CliGet. They do not conflict, they are complement each other. In short, if you want to manage development environment, use asfd. If you want to install small tools, use CliGet. They do not conflict, they are complement each other.
#### I already use the package manager of my OS to install tools, why would I need cliget ? #### I already use the package manager of my OS to install tools, why would I need cliget ?
Package managers handle dependencies and install software system wide, for all users. Not all sofwares are packaged for all OS distributions because this is hard work for mantainers. So you end up with some softwares not available or not up to date. Package managers handle dependencies and install software system wide, for all users. Not all softwares are packaged for all OS distributions because this is hard work for maintainers. So you end up with some softwares not available or not up to date.
CliGet only install standalone programs, in the user profile (`.local/bin`). It does its best to find the last version and the best way to install the software. The is no need to package for CliGet. CliGet only install standalone programs, in the user profile (`.local/bin`). It does its best to find the last version and the best way to install the software. The is no need to package for CliGet.
#### I already use Flatpack, AppImage, Snap to install tools in my profile, why would I need CliGet ? #### I already use Flatpack, AppImage, Snap to install tools in my profile, why would I need CliGet ?
These are package managers for the user profile. They come with heavy runtime. And, as classic package manager, not all tools are packaged nor up to date as it requires work from mantainers. These are package managers for the user profile. They come with heavy runtime. And, as classic package manager, not all tools are packaged nor up to date as it requires work from maintainers.
CliGet does not sandbox, nor manage dependencies but does not any special packaging. CliGet does not sandbox, nor manage dependencies but does not any special packaging.
#### I don't want to install python on my machine #### I don't want to install python on my machine
CliGet is written in Python but packaged as a standalone program with no dependencies except lic and zlib. CliGet is written in Python but packaged as a standalone program with no dependencies except `libc` and `zlib`.
#### I don't trust you. What prevent you from dumping me a malware instead of a genuine software ? #### I don't trust you. What prevent you from dumping me a malware instead of a genuine software ?
@ -105,4 +105,4 @@ CliGet is written in Python but packaged as a standalone program with no depende
#### I want this for macos or mswindows #### I want this for macos or mswindows
Currently only Linux is supported. It shoud work on all unix like OS. For others, contributions are wellcome as long as they do not compicate the tool too much. Currently only Linux is supported. It should work on all Unix like OS. For others, contributions are welcome as long as they do not complicate the tool too much.