Provide os2-rpm package

[dmik]

Currently, we put all OS/2 platform specific stuff right in the RPM source tree (and binary distribution) itself. But this doesn't look correct as this stuff is highly platform-specific and RPM per se should be kept as generic as possible.

Fedora does the same by providing the redhat-rpmbuild-macros package (check ​http://pkgs.fedoraproject.org/cgit/rpms/redhat-rpm-config.git/tree/).

This can be rather easily implemented by putting all platform-specific macros (and scripts) to /@unixroot/etc/rpm where they are automatically picked up by RPM as it's a standard directory for searching platform-specific macros. This directory may also be used by other packages to extend RPM functionality without the need to modify RPM itself.

Current candidates for inclusion in os2-rpm-config:

• entire platform/*-os2-*/macros tree
• wps_* and warpin_* macros (and their respective scripts, wps-object and warping-conflicts)
• other os2_* macros (including cube, the CONFIG.SYS processor)
• brp-strip.os2 script
• find-legacy-runtime.sh script

Note that when moving scripts to /etc/rpm, their path in macros should be updated accordingly.

[dmik]

Note that doing so will save us a lot of time because many our RPM-related changes don't touch RPM itself but instead touch OS/2 platform-specific bits and when it's separated it can be released separately.

[dmik]

It makes sense to start building such a package next time a change to the OS/2 platform specific bits is made.

[dmik]

Note that there are some hard-coded highly OS/2 platform specific things now, like this one: http://trac.netlabs.org/rpm/ticket/135. Such things need to go away for this ticket to be considered solved.

[dmik]

I renamed the package to just os2-rpm and the first version is released, see source:spec/trunk/SPECS/os2-rpm.spec​. The reason for a rename is that we will split macros and scripts required for installing packages (like the WPS and WarpIn ones) - these will leave in os2-rpm - and the ones needed for building - these are already in os2-rpm-build (all generated from a single .spec).

Note that we should either add os2-rpm to bootstrap or make it a dependency of os2-base. As for os2-rpm-build, this will be a dependency of some meta package like os2-devel which will gather all mandatory things necessary for development using our tool chain.

[Silvan Scherrer]

we need to add those rpm asap as a req to os2-base or whichever. As else no one (beside us) knows this rpm is needed.

[dmik]

This is done in os2-base-0.0.0-16 which now requires os2-rpm >= 0-2. I guess we may close this ticket as the initial goal is reached.