The main justification I've seen for Toolbx over Distrobox has been the former is written in Go, the latter in shell. Given this will wipe out that argument, I'm sincerely curious what ends up happening with Toolbx. It's lagged on features and workflows for quite awhile, and, while there's been definite movement, Distrobox still is way ahead on most axes.
I look forward to saner logging beyond the current "implementation" of bash set -x. When I look at the output of a command like distrobox enter foo --verbose, I tend to see stuff like this repeating ad nauseam:
+ read -r line
+ case "${line}" in
+ IFS=
+ read -r line
+ case "${line}" in
+ IFS=
+ read -r line
+ case "${line}" in
+ IFS=
gecko | a day ago
The main justification I've seen for Toolbx over Distrobox has been the former is written in Go, the latter in shell. Given this will wipe out that argument, I'm sincerely curious what ends up happening with Toolbx. It's lagged on features and workflows for quite awhile, and, while there's been definite movement, Distrobox still is way ahead on most axes.
kamme | a day ago
I understand the why, but I'll miss just looking at the bash source when I have an issue. I can read go, but it's just not the same.
I am however a happy user of distrobox, it's really nice and fills a need.
aminom | 21 hours ago
I look forward to saner logging beyond the current "implementation" of bash
set -x. When I look at the output of a command likedistrobox enter foo --verbose, I tend to see stuff like this repeating ad nauseam: