| 1 | | An obvious solution is to only delete WPS objects in %postun if $1 is 0 (i.e. the last version of the package is removed). When it is not 0, it's not a removal, it's an update, and the objects should not be deleted. This, in turn, means that when creating objects in %post, we should first delete them if $1 is not 0 (i.e. upon update) and only after that create them again (to make sure the old objects not intended to exist after the update will go away). Quite cumbersome. A clear RPM flaw to me. |
| | 1 | An obvious solution is to only delete WPS objects in %postun if $1 is 0 (i.e. the last version of the package is removed). When it is not 0, it's not a removal, it's an update, and the objects should not be deleted. This, in turn, means that when creating objects in %post, we should first delete them if $1 is not 0 (i.e. upon update) and only after that create them again (to make sure the old objects not intended to exist after the update will go away). Quite cumbersome. |
| | 2 | |
| | 3 | This actually applies to any other setting (e.g. CONFIG.SYS change, INI change, etc, etc, etc). This looks like a clear RPM design flaw to me. |
