What does "Not Updatable" tag actually mean in your context

[numericOverflow]

Looks like there's a definition on updatable in this recent commit, but we don't have one for Not Updatable
Sorry if this seems like a stupid question, but just looking for clarification. I get that updatable means that the setup script will do it automagically, but how do you define the Not updatable tag?

I assume it generally means that any updates must be made via software package within the container/VM itself, but how strong is your suggestion:

• It's fine to manually update app, just not official supported by community-scripts installer
• It might be possible to manually update, but not recommended and we won't help when it breaks
• Seriously, don't do it because very bad things will happen

[tremor021]

Updatable = the script author implemented the update procedure into the script
Not Updatable = the author of the script didn't provide a update procedure or the app itself has a breaking change which results in us forcibly stopping any update on the app.

Most of the apps that we install are pulled from github, via release tarballs. This ensures that app most likely has a way of updating without forcing the user to reinstall the app.

However, some apps introduce big changes to the way the app installs/updates/works, so the current update procedure would most likely break the entire LXC if used. For such apps we reserve a right to outright stop supporting it because of constant breaking, or we don't give the user option to update such apps until the developer starts making a stable, predictable release model.

[numericOverflow]

Got it. That's about what I figured.

Any way for users to know which Not Updatable applies (UpdatesNotYetImplemented or UpdatesCauseBreakage)?

Is it relatively reasonable to assume UpdatesNotYetImplemented unless UpdatesCauseBreakage is explicitly specified?

[tremor021]

Any way for users to know which Not Updatable applies (UpdatesNotYetImplemented or UpdatesCauseBreakage)?

For the end user it really doesn't matter, he won't be getting the update anyway.

Is it relatively reasonable to assume UpdatesNotYetImplemented unless UpdatesCauseBreakage is explicitly specified?

If the app is tagged as Not updatable, its most likely that the developers didn't document a way to safely do updates. Not updatable because its causing breakage is rarely the case. Only a handful of apps really give such headaches to both script maintainers and users.