^as you're already touching this, could you sort it like

USE_QT= <build and run depends> \
                   <build_only_depends> \
                   <run_only_depends>

^ in app updates are supported?

^ that's a bit too short -- I'd make it live until before the next quarterly is cut (Q3) -- so june-ish.

The main UI flashes a "check for a new version of Shotcut" when one exists, so kind of

If this new shotcut ends up in Q2 ie committed before the cut, webvfx should not follow it there

^ öh, do we allow in-app updates? -- wouldn't it make more sense to simply disable that functionallity if possible?

^not strictly necessary

You can commit the changes to multimedia/webvfx-qt5 to the tree directly, not as part of this review.

^ I'd suggest to make it 2022-09-30 -- i.e. the end of Q3.

Not able to be disabled, this is hardcoded into mainwindow.cpp

Does not make sense to deprecate before shotcut update is committed, thus both should be committed together

Once shotcut update gets committed, there are no more consumers. This should have been removed long ago

^ more a general idea to think about... not everyone is a native english speaker, and some prefer to have their applications in the native language. So shouldn't NLS be on by default?

... so it should have been removed long ago, but it makes no sense to mark it a such... okay...

I'll let you think about it for a while...

NLS is a default in the framework globally I'm pretty sure

It doesn't make sense to deprecate or remove until any shotcut using mlt7 (which at the same time deprecated and removed webvfx from dependencies) gets committed in the tree.