Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I provide an RPM package that contains both 32-bit and 64-bit applications, and can be installed in either mode, i.e. on both 32-bit and 64-bit platforms.

As the package contains both applications, when trying to install the RPM package on a 32-bit Linux machine it creates soft links for 64-bit applications too, along with the 32-bit application. During post-install I remove the soft-links for the 64-bit application as we cannot install it on a 32-bit machine.

Unfortunately, although the package is already installed on the 32-bit machine, and I have removed the soft links for the 64-bit application as a part of the post-install, the RPM still contains info for these 64-bit application soft links, which can be seen when queried through the rpm command but which in reality are not present.

How can I query through rpm and remove the extra info for a 64-bit application? This should be done during installation of the 32-bit package, but may be done in post-install.

share|improve this question
Wait, you have one package that provides both archs? – Ignacio Vazquez-Abrams Sep 27 '12 at 2:30
Yes, one package that can install on both 32-bit and 64-bit linux. – user1982 Sep 29 '12 at 17:20

The obvious solution is to not include the symlinks in the RPM package itself, but to create them as needed by the RPM's post-install script.

i.e. the post-install script should check the host's architecture. if 32-bit then create symlinks for 32-bit (if needed), else if 64-bit then create symlinks for 64-bit.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.