diff --git a/CHANGELOG.md b/CHANGELOG.md index 8769b638..dfbafedc 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -100,7 +100,8 @@ Versioning](https://semver.org/spec/v2.0.0.html). directories, not just directories that are called `VST3`. This, of course, should not be needed. - The previously deprecated symlink installation method has now been removed - from yabridgectl, along with the `yabridgectl set --method` option. + from yabridgectl, along with the `yabridgectl set --method` option. The + terminology in `yabridgectl status` has changed accordingly. - `yabridgectl status` now lists the architecture of `libyabridge-chainloader-vst2.so` just like it already did for the VST3 library. diff --git a/tools/yabridgectl/src/actions.rs b/tools/yabridgectl/src/actions.rs index 60b78e9a..ea433869 100644 --- a/tools/yabridgectl/src/actions.rs +++ b/tools/yabridgectl/src/actions.rs @@ -172,14 +172,14 @@ pub fn show_status(config: &Config) -> Result<()> { ), }; - // TODO: With the symlink installation method gone this does not make a lot of sense - // anymore, but it does seem useful to have some sort of label telling you that a - // plugin has been set up + // This made more sense when we supported symlinking `libyabridge-*.so`, but we should + // display _something_ to indicate that the plugin is set up correctly let status_str = match status { - Some(NativeFile::Regular(_)) => "copy".green(), - Some(NativeFile::Symlink(_)) => "symlink".green(), + Some(NativeFile::Regular(_)) => "synced".green(), + // This should not occur, but we'll display it just in case it does happen + Some(NativeFile::Symlink(_)) => "symlink".yellow(), Some(NativeFile::Directory(_)) => "invalid".red(), - None => "not yet installed".into(), + None => "not yet synced".into(), }; println!(