diff options
author | Jan200101 <sentrycraft123@gmail.com> | 2020-11-21 18:54:17 +0100 |
---|---|---|
committer | Jan200101 <sentrycraft123@gmail.com> | 2020-11-21 18:54:17 +0100 |
commit | 31c9d3590337f612662cfbe542c80e96c84299a0 (patch) | |
tree | 9b1cedaf0f7f2011501ed82d19f8b34dbb722bd3 | |
parent | b5aaac8349f504f81124e71a4bcf2003cc6d7800 (diff) | |
download | polecat-31c9d3590337f612662cfbe542c80e96c84299a0.tar.gz polecat-31c9d3590337f612662cfbe542c80e96c84299a0.zip |
Update readme (once again), add message for no installer found
-rw-r--r-- | README.md | 17 | ||||
-rw-r--r-- | src/lutris.c | 6 |
2 files changed, 14 insertions, 9 deletions
@@ -1,20 +1,21 @@ # polecat -- *What is polecat?* -polecat is wine manager +- *What is polecat?* +polecat is wine manager that manages, installs and downloads wine for you. +It also works with Valves Proton and just requires you to drag drop the Proton Wine into data directory as output by `polecat env` -- *Why?* +- *Why?* I'm not satified with the quality of lutris and how its maintained. It feels like almost every week there is a regression or other problem caused by not enough testing and sanity checking being done. A week before I made polecat I fed up with Lutris constantly breaking on me and having to wait for a fix to land on the master branch -I looked up how lutris fetched wine and DXVK versions and implemented them in C with libcurl to download stuff, json-c to parse the API (and later a config file) and libarchive to unpack the downloaded archives for wine and DXVK. +I looked up how lutris fetched wine and DXVK versions and implemented them in C with libcurl to download stuff, json-c to parse the API (and config files in the future), and libarchive to unpack the downloaded archives for wine and DXVK. -- *Why should I use polecat instead of XYZ?* +- *Why should I use polecat instead of Lutris/XYZ?* You probably shouldn't. -Polecat is intended to be used by power-users that know how to deal with wine willing to troubleshoot when shit goes down. +Polecat is intended to be used by power-users that know how to do things by hand and deal with them when they break. -- *What about installers/other lutris features* -lutris support is planned to be added but there is a lot to deal with that is easier to do in a higher level language like Python. +- *What about installers/other lutris features* +lutris support is planned and parsing of installers into an internal struct has already been added (as can be seen by invoking `polecat lutris info <installer-name>`) but it won't be here for a long time or until a large crowd of people convince me to do it faster. ## Dependencies diff --git a/src/lutris.c b/src/lutris.c index 61a98c7..c57c866 100644 --- a/src/lutris.c +++ b/src/lutris.c @@ -195,11 +195,15 @@ int lutris_info(int argc, char** argv) } else { - + printf("Couldn't find an installer by the name `%s'\n", argv[1]); } lutris_freeInstaller(&installer); } + else + { + puts(USAGE_STR " lutris info <installer-name>\nThe Name of an installer can be found by viewing the install script of an installer"); + } return 0; } |