Overwriting policy in upgrading

[Takeshi NISHIMURA]

On 2016/12/20 2:55, Cantor, Scott wrote:
>
> While I appreciate that people want everybody's installs to be "clean", I think that's just ultimately unrealistic once a system gets into production. The webapp thing is just a bug but the rest is something we're deliberate about. You do not have to merge in changes unless you need to enable a feature that wasn't in the version you originally installed, and we do try to document the changes required to enable something of that sort.

New features would be, but some bug fixes and improvements would not, at least for *.vm files.
I wonder whether IDP-986 is effective without overwriting ldap-authn-config.xml.

> We almost never remove a file unless we're talking about a major upgrade. The messages files are among the very few examples I can think of.

Except for messages files, three files are removed since 3.1.2. It is confusing if they remain in /opt/shibboleth-idp/views/ and the last one will prevent future updates of that in system/views/.
Only in shibboleth-idp-3.1.2/dist/views: logout-response.vm.dist
Only in shibboleth-idp-3.2.1/dist/views: expiring-password.vm.dist
Only in shibboleth-idp-3.2.1/dist/views: resolvertest.vm.dist

Best regards,
Takeshi

> I appreciate that consistency makes support easier, but I just don't think it's common enough. Most of the time people either edit the files and make it impossible to automate these changes you would be trying to make, or they're operating the software in such a limited way that they wouldn't care about the new features anyway.
>
> -- Scott