Create /run/.toolbxenv file#1725
Conversation
|
Build succeeded. ✔️ unit-test SUCCESS in 2m 09s |
It's difficult to explain to people integrating with Toolbx why they have to look at /run/.toolboxenv to see if they are in a Toolbx container. :) Create this, but leave /run/.toolboxenv around as a legacy file as well. Updates any references to the short name. containers#1399 containers#1725 Signed-off-by: Ian Wienand <iwienand@redhat.com>
debarshiray
left a comment
debarshiray
left a comment
There was a problem hiding this comment.
Oops, I completely forgot about this pull request. My apologies.
Thanks for the carefully constructed PR, @ianw ! I will rebase on top of main and merge once the CI passes.
debarshiray
force-pushed
the
toolbxenv
branch
from
1e8ee59 to
97e5dee
Compare
I took the liberty to tweak the subject of the commit message and added a link to #1399 to make it easier to track all the rename the project changes across time and Toolbx releases. |
|
Build failed. ✔️ unit-test SUCCESS in 2m 23s |
|
recheck |
This looks like a passing infrastructure or network problem: |
|
Build succeeded. ✔️ unit-test SUCCESS in 2m 15s |
2 participants
It's difficult to explain to people integrating with toolbx why you have to look at
/run/.toolboxenvto see if you're in a toolbx :)Create this, but leave
/run/.toolboxenvaround as a legacy file as well. Updates any references to the short name.