| | 442 | === Creating fake WarpIN database entries === |
| | 443 | Some packages still distributed as WarpIN packages (WPI) now depend on packages distributed via rpm/yum. |
| | 444 | In order to make these WPI packages happy, it is possible to let the rpm/yum package create fake entries in the WarpIN database. |
| | 445 | |
| | 446 | wpi4rpm will fake the vendor and the package name to "wpi4rpm", get the appropriate app name and translate the version from rpm/yum into a version number scheme supported by WarpIN. Most notably version numbers, which have letters are translated into 99. The filelist and several other fields hold dummy entries. |
| | 447 | |
| | 448 | This is done the following simple way: |
| | 449 | {{{ |
| | 450 | %post |
| | 451 | if [ "$1" -ge 1 ]; then # (upon update) |
| | 452 | wpi4rpm del "%{name}" %{version}-%{release} |
| | 453 | fi |
| | 454 | wpi4rpm add "%{name}" %{version}-%{release} |
| | 455 | |
| | 456 | %postun |
| | 457 | if [ "$1" -eq 0 ]; then # (upon removal) |
| | 458 | wpi4rpm del "%{name}" %{version}-%{release} |
| | 459 | fi |
| | 460 | }}} |
| | 461 | |
| | 462 | Note: The purpose of this utility is not to enable to uninstall rpm/yum packages using WarpIN, but only to fake the presence of a certain WarpIN package to the installation of other WarpIN packages. Removing the database entries using WarpIN is possible, while verification and deinstallation will fail. This works as designed. |
