b***@freebsd.org
2018-06-28 16:35:03 UTC
Bugzilla Automation <***@FreeBSD.org> has asked freebsd-pkg mailing list
<***@FreeBSD.org> for maintainer-feedback:
Bug 229393: ports-mgmt/pkg: Show which options changed if upgrade needed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229393
--- Description ---
`pkg upgrade` detects changed options in a package and requires reinstallation,
but only shows minimal information about the reason:
Installed packages to be REINSTALLED:
mypackage-1.11 (options changed)
This patch prints before/after options and their values so the sysadmin can
clearly see why a package is reinstalled.
Why? Building production packages yourself with regular ports tree updates and
custom options can often lead to this case, and when doing live deployments,
you want to be sure that no critical options have been altered.
I wanted to combine this with {-v,--verbose}, but apparently `pkg upgrade
{-v,--vulnerable}` already exists, overriding the default expectation of 'v'
option meaning verbose.
<***@FreeBSD.org> for maintainer-feedback:
Bug 229393: ports-mgmt/pkg: Show which options changed if upgrade needed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229393
--- Description ---
`pkg upgrade` detects changed options in a package and requires reinstallation,
but only shows minimal information about the reason:
Installed packages to be REINSTALLED:
mypackage-1.11 (options changed)
This patch prints before/after options and their values so the sysadmin can
clearly see why a package is reinstalled.
Why? Building production packages yourself with regular ports tree updates and
custom options can often lead to this case, and when doing live deployments,
you want to be sure that no critical options have been altered.
I wanted to combine this with {-v,--verbose}, but apparently `pkg upgrade
{-v,--vulnerable}` already exists, overriding the default expectation of 'v'
option meaning verbose.