chore: cleanup

This commit is contained in:
iff 2024-12-12 16:52:11 +01:00
parent 3c10dc2d7c
commit 461b07a116
4 changed files with 11 additions and 5 deletions

View file

@ -16,6 +16,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- AI module: - AI module:
- Allow multiple suggestions - Allow multiple suggestions
- More default values - More default values
### Changed
- Compile-time `_PR_LIB` changed to `_DEF_PR_LIB` to be explicit - Compile-time `_PR_LIB` changed to `_DEF_PR_LIB` to be explicit
## [0.6.3] 2024-12-11 ## [0.6.3] 2024-12-11

View file

@ -208,9 +208,9 @@ An API key is included with the source. It should always work unless I can no lo
> - `_DEF_PR_AI_URL` > - `_DEF_PR_AI_URL`
> - `_DEF_PR_AI_MODEL` > - `_DEF_PR_AI_MODEL`
> >
> If the default values were not provided, pay-respects' own values will be used. Your request will be filtered to avoid abuse usages. Request will then be forwarded to a LLM provider that will not use your data for training. > If default values were not provided, pay-respects' own values will be used. Your request will be filtered to avoid abuse usages. Request will then be forwarded to a LLM provider that will not use your data for training.
>
> </details> </details>
## Contributing ## Contributing

View file

@ -167,7 +167,7 @@ pub fn get_packages(
} }
false => { false => {
eprintln!("{} Unsupported package manager", ":pay-respects".yellow()); eprintln!("{} Unsupported package manager", ":pay-respects".yellow());
return None; None
} }
}, },
} }

View file

@ -44,10 +44,13 @@ Expose your module as executable (`chmod u+x`) in `PATH`, and done!
## `LIB` directories ## `LIB` directories
If exposing modules in `PATH` annoys you, you can set the `_PR_LIB` environment variable to specify directories to find the modules, separated by `:` (analogous to `PATH`). The variable can be set either runtime or compile-time. If exposing modules in `PATH` annoys you, you can set the `_PR_LIB` environment variable to specify directories to find the modules, separated by `:` (analogous to `PATH`):
Example in a [FHS 3.0 compliant system](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s06.html): Example in a [FHS 3.0 compliant system](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s06.html):
```shell ```shell
# compile-time
export _DEF_PR_LIB="/usr/lib:$HOME/.local/share"
# runtime
export _PR_LIB="/usr/lib:$HOME/.local/share" export _PR_LIB="/usr/lib:$HOME/.local/share"
``` ```
This is not the default as there is no general way to know its value and depends on distribution (`/usr/lib`, `/usr/libexec`, `/data/data/com.termux/files/usr/libexec`, etc.). System programs usually have a hard-coded path looking for `lib`. If you are a package maintainer for a distribution, setting this value when compiling, so it fits into your distribution standard. This is not the default as there is no general way to know its value and depends on distribution (`/usr/lib`, `/usr/libexec`, `/data/data/com.termux/files/usr/libexec`, etc.). System programs usually have a hard-coded path looking for `lib`. If you are a package maintainer for a distribution, setting this value when compiling, so it fits into your distribution standard.