- robatino - I simplified the instructions for the 32-bit wrapped plugin in 64-bit Fedora, by specifying two yum install commands, instead of one. The intent is that the first command will pull in the 32-bit libstdc++, which will prevent Adobe Reader from being pulled in as a dependency. But I'm worried that if the Adobe repo is enabled before the first command is run, the Reader might get pulled in anyway, instead of libstdc++. If this is possible, then I should modify the instructions so the Adobe repo is only enabled after the first yum install command. Anyone know?) In any case, it shouldn't be necessary to exclude the Adobe Reader. It's just a matter of getting 32-bit libstdc++ installed - after that, everything should be fine.)
- robatino - I tried enabling the Adobe repo in 64-bit Fedora 10, 11, 12, 13, 14, and Rawhide, then running the first command. It never pulled in Adobe Reader. That doesn't prove that it can't happen (say, with a different set of packages either installed or in the repos), though, so would still like to hear from anyone who knows for sure.
Adding Section About Switching Between Plugins
I want to add this to the guide but I'm new to the wiki, so I wanted to ask first if it's suitable. Here is it...
If you want to switch between 32 and 64 bit Versions, after you have installed both. You can switch between them by renaming the file /usr/lib/flash-plugin/libflashplayer.so and then the system will use the library in ~/.mozilla/plugins/ where 64bit library is. To restore the 32 wrapped version you can just rename it back and firefox should use it. After every Change firefox have to be restarted.
PackageKit-gtk-module.i686 also needed for 32-bit wrapped version?
I had to install also PackageKit-gtk-module.i686 on Fedora 14 x86_64, as described in http://lists.fedoraproject.org/pipermail/users/2010-October/384280.html by another user. Probably it should also be mentioned. - nsoranzo