as a "deployer" I'd like to be able to override CONFIG_FILE so that instead of directly updating ~/.bashrc, another file would be created, and then loaded into ~/.bashrc (or whatever).
for example, I'd like to have bash-it config file at ~/.bash.d/scripts/bash-it.bash, and load it from ~/.bashrc.
This "feature" has a side-effect of easily allowing to compare resulting .bashrc file with an expected value, thus allowing testing.
Current behavior
currently install.sh determines CONFIG_FILE value based on OSTYPE at line 188.
Possible solution
Introduce an env variable BASH_IT_CONFIG_FILE, if defined, set CONFIG_FILE to its value.
Expected behavior
as a "deployer" I'd like to be able to override
CONFIG_FILE
so that instead of directly updating~/.bashrc
, another file would be created, and then loaded into~/.bashrc
(or whatever).for example, I'd like to have bash-it config file at
~/.bash.d/scripts/bash-it.bash
, and load it from~/.bashrc
.This "feature" has a side-effect of easily allowing to compare resulting
.bashrc
file with an expected value, thus allowing testing.Current behavior
currently
install.sh
determinesCONFIG_FILE
value based onOSTYPE
at line 188.Possible solution
Introduce an env variable
BASH_IT_CONFIG_FILE
, if defined, setCONFIG_FILE
to its value.Context
currently (the lack of thereof requires me to):
hopefully I'd be able to:
Notes
I can implement the above.