mirror of
https://github.com/flatcar/scripts.git
synced 2025-09-22 22:21:10 +02:00
cea18c41c3
The scripts that invoked `cros_workon` without specifying a path to the script were not calling the internal `cros_workon` directly, but rather a copy installed in `/usr/bin/cros_workon`. `/usr/bin/cros_workon` comes from the `coreos-base/cros-devutil` and is a wrapper script that sources `common.sh` file to figure the location of the `scripts` and finally invokes the internal `cros_workon`. Curious thing is that the sourced `common.sh` comes from the `/usr/lib/crosutils` directory and contents of the directory come from the `dev-util/crosutils` package. And that `common.sh` is different from the one in the scripts directory, but fortunately the part that detects the path to the `scripts` directory is the same. I'm not sure where where exactly the copy of `common.sh` in `/usr/lib/crosutils` comes from - likely from somewhere in `https://chromium.googlesource.com/chromiumos/platform/crosutils`. Just cut the middle layers and call the internal copy of `cros_workon` directly.
Flatcar Container Linux SDK scripts
Welcome to the scripts repo, your starting place for most things here in the Flatcar Container Linux SDK. To get started you can find our documentation on the Flatcar docs website.