On Wed, Nov 4, 2009 at 6:06 PM, Michal Jaegermann <michal@xxxxxxxxxxxx> wrote: > On Wed, Nov 04, 2009 at 10:38:51AM -0700, Petrus de Calguarium wrote: >> >> My actions: >> >> I unpacked the tarball and put libflashplayer.so into >> /usr/lib64/mozilla/plugins. > > Quite likely this will get you into future troubles when eventually > an rpm-package version will appear; unless you will remove all > traces of libflashplayer from your system before attempting an > installation of such package. Immitating a layout of existing > packages, i.e. libflashplayer.so in /usr/lib64/flash-plugin/ and a > link in /usr/lib64/mozilla/plugins is likely safer. SElinux will complain a lot if you place it there manually. You can safely place it in $HOME/.mozilla/plugins/ >> Does nspluginwrapper automatically detect the addition >> of a plugin and 'wrap' it? > > No. Package scripts will do that job. What selinux will do with > this is another question. A run of restorecon may help with > labelling. If you're installing a 64 bit plugin in a 64 bit browser, you don't need nspluginwrapper. IIRC you can just use it (if not, just figure out how to install a normal plugin). Cheers, Renato >> The nspluginwrapper documentation states that one run: >> >> nspluginwrapper -i > > That script is really called mozilla-plugin-config. See this: > $ rpm -ql nspluginwrapper.x86_64 | grep /bin > and try > > mozilla-plugin-config -h > > for more information. > > Michal > > -- > fedora-test-list mailing list > fedora-test-list@xxxxxxxxxx > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
