Hi
What Martin was talking about was RPM-izing legacy type OS/2 apps. That has lots of benefits, and some downsides.
I insist it is not a "all or nothing" effort, or that it is going to replace the common way to distribute software in zip/wpi files. It is just trying to "RPM-izing" what can actually work, there will be OS/2 apps that do not work under the RPM path structure and some that don't. It is going to be impossible for me alone to convert all OS/2 apps to have a RPM/YUM install alternative, so help will be always welcome. I also respect the choice of people that like to have the zip and wpi files and want to have the control on where files are stored, but on the present time, it seems that a lot of people does not care where the installer stores the .dll and files, just care the apps works and provide him some service.
But I still haven't full started with the RPM installers. On my last attempts I got stuck with the WPS integration to create icons and set the properties of WPS objects (Path, working directory, etc). I usually get the answer that it works, but I'm doing it wrong, but nobody tells me how to do it right.
The other things that drives me crazy on the specs files is to know the variable names for the paths (directories) and the fights with the slashes and backslashes. I had even made
this quick list to try to remember the names of variables.
Regards.
