While it seems relatively traceable what the script does, this is an annoyance.
I installed on Alpine Linux which uses musl libc, and found the tool relatively
useless and running awrit <url> will just exit without any meaningful error.
This is most likely due to me having the glibc compatibilty layer installed,
e.g., running a glibc-built chromium with that layer, will usually fail.
Instead of spending time debugging the issue, I wanted to uninstall the tool.
You don't make this easy enough & install dependencies e.g. Bun.
The installer should touch some files in the (always cloned?) repository folder,
which can be added to .gitignore, tracing what was done during installation,
and offer a flag that can backtrack to restore the initial environment.
EDIT - OK, it appears all dependencies are contained in DOWNLOAD_TO
& INSTALL_TO, so this is not completely awful to remove, only inconvinient.
If this is truly always the case, adding an Uninstalling section to the
readme is all that would need to be done.
While it seems relatively traceable what the script does, this is an annoyance.
I installed on Alpine Linux which uses musl libc, and found the tool relatively
useless and running
awrit <url>will just exit without any meaningful error.This is most likely due to me having the glibc compatibilty layer installed,
e.g., running a glibc-built
chromiumwith that layer, will usually fail.Instead of spending time debugging the issue, I wanted to uninstall the tool.
You don't make this easy enough & install dependencies e.g. Bun.
The installer should touch some files in the (always cloned?) repository folder,
which can be added to
.gitignore, tracing what was done during installation,and offer a flag that can backtrack to restore the initial environment.
EDIT - OK, it appears all dependencies are contained in
DOWNLOAD_TO&
INSTALL_TO, so this is not completely awful to remove, only inconvinient.If this is truly always the case, adding an Uninstalling section to the
readmeis all that would need to be done.