As stated, you better get the 32bit versions of those packages, rather than rpm2tgz them. That should be a very very very last resort, and since those packages are available for 64 bit, one can rightfully assume they're available on 32 bit as well.
For libraries, if they adhere to the FHS: 64bit libraries are installed to the libdir with a suffix 64. e.g. /lib64 and /usr/lib64; 32bit libraries are to be installed to such directories without the "64" suffix.
Be sure you do NOT upgrade the existing package; for example you have libpango-1.2.3-x86_64-1alien.txz installed, you do NOT do upgradepkg libpango-1.2.3-i486-1alien.txz, but you do installpkg libpango-1.2.3.-1alien.txz; In this way you have both libraries existing next to each other.
Prior to installation, you can check if files would be overwritten:
Code:
PKGSUFFIX=txz # it's either tgz or txz, fill in what you have.
PKG64=gtkglext-1.2.3-x86_64-1tag.${PKGSUFFIX} # fill in the 64bit package name (without the .t?z extension)
PKG32=gtlglext-1.2.3-i486-1tag.${PKGSUFFIX} # fill in the 32bit package name (without the .t?z extension)
case ${PKGSUFFIX} in
txz)
TAR_PARAM=J
;;
tgz)
TAR_PARAM=z
;;
*)
echo "PKGSUFFIX must be either tgz or txz"
;;
esac
tar ${TAR_PARAM}tf ${PKG64} | while read fn
do
tar ${TAR_PARAM}tf ${PKG32} | grep ${fn}
done
Any output of this will be a file that would be overwritten; Any binary executable or library is a bad idea (tm) here. I would not worry overmuch about documentation, as that should be more or less the same. If you fear that there may be some issues with installing the 32bit version over the 64bit version, you probably want to extract the 32bit package and move the files about so that they will not overwrite existing files and run makepkg again to make a nice new package. If that's too advanced, you come back here with your questions ;-)
