Closed rucker closed 8 years ago
What I'll probably need to do is create a step in the process to specifically build $PATH
per local config before compiling bashcommon, bash${PLATFORM}, and bash_private.
This will probably be useful anyway if I want to handle Mac systems that don't use the GNU coreutils.
Since I will now have two versions of bash_profile
(one for GNU coreutils and one for BSD), that file will now change somewhat arbitrarily depending on the system I've been using recently. To avoid this, I should compile to a bash_aliases file and then source it from bash_profile.
Then again, this would defeat part of the purpose of this project, which is to show off my bash files. I could conceivably compile those aliases straight into the bash_profile under version control, but take the approach described above for the version in ~. This, however, sounds overly complex.
As a workaround to resolve #21, the line
eval 'dircolors'
was moved to bash_private. This line really belongs in bash_common. A change should be made that resolves this conflict.