Documenting here for the future. I do not plan to fix this anytime soon.
In issue #6 I merged the ~/bin repo into this repo under ~/.bin. However, this retroactively breaks all scripts prior to this commit which source the ~/bin directory.
There are really only two solutions. But they both involve iterating through all commits prior to 5e176c3:
- Iterate through all commits, read all files, and replace all instances of
~/bin with ~/.bin, and $HOME/bin with $HOME/.bin.
- Iterate through all commits and move all files in ~/bin to /.bin.
I am not sure which approach is easier, but the second one is certainly more correct.
Eventually I do want to tag previous major version (i.e. v2025, v2024, etc.) for both posterity and also for simpler version tracking. However, this issue will need to be fixed all versions previous to 2025 to be valid.
It is a shame since I could have easily avoided all of this had I just merged the repo into the correct directory, but I genuinely did not forsee this.
Documenting here for the future. I do not plan to fix this anytime soon.
In issue #6 I merged the
~/binrepo into this repo under~/.bin. However, this retroactively breaks all scripts prior to this commit which source the~/bindirectory.There are really only two solutions. But they both involve iterating through all commits prior to 5e176c3:
~/binwith~/.bin, and$HOME/binwith$HOME/.bin.I am not sure which approach is easier, but the second one is certainly more correct.
Eventually I do want to tag previous major version (i.e. v2025, v2024, etc.) for both posterity and also for simpler version tracking. However, this issue will need to be fixed all versions previous to 2025 to be valid.
It is a shame since I could have easily avoided all of this had I just merged the repo into the correct directory, but I genuinely did not forsee this.