Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#9491 - mplayer-plugin $MOZ_PLUGIN_PATH
Attached to Project:
Arch Linux
Opened by Ray Rashif (schivmeister) - Thursday, 07 February 2008, 23:24 GMT
Last edited by Alexander Baldeck (kth5) - Wednesday, 13 February 2008, 12:00 GMT
Opened by Ray Rashif (schivmeister) - Thursday, 07 February 2008, 23:24 GMT
Last edited by Alexander Baldeck (kth5) - Wednesday, 13 February 2008, 12:00 GMT
|
DetailsPackage:
mplayer-plugin 3.50-1 Issue: The variable in question (as per summary), used in the packaging process, has a certain flaw where if the user's rendition of the path includes more than one directory, any separation character (in this case ":") will be captured. This leads to the creation of a redundant file/directory with the character being part of the name, among other potential problems. Case: >>$ echo $MOZ_PLUGIN_PATH >>$ /opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins So from line 25 of the PKGBUILD, mkdir -p $startdir/pkg/${MOZ_PLUGIN_PATH} the user will have an "/opt/mozilla/lib/plugins:" directory. This produces a further redundancy as currently the packager only installs essential files to a specific directory. From PKGBUILD line 31, install -m755 mplayerplug-in*so ${startdir}/pkg/usr/lib/mozilla/plugins Thus, "/opt/mozilla/lib/plugins:" and any other paths involved in $MOZ_PLUGIN_PATH will be empty. |
This task depends upon
Please don't use MOZ_PLUGIN_PATH at all in the PKGBUILD!
It's just that the value of $MOZ_PLUGIN_PATH will be taken as one path. So you should probably just install directly to /usr (better, since we're on transition) or /opt. At least browsers like Firefox, Flock, and Opera can automatically detect those, but not this faulty one. Even if they do, there may be other issues. Well it's just something minor but can't be ignored either :)
> The latest package is further fubarred.
Same here. mplayer-plugin 3.50-2 is worse than 3.50-1 :(
[crc64@Arch pkg]$ tar -tf mplayer-plugin-3.50-2-i686.pkg.tar.gz
.PKGINFO
.INSTALL
etc/
etc/mplayerplug-in.conf
opt/
opt/mozilla/
opt/mozilla/lib/
opt/mozilla/lib/plugins:/
opt/mozilla/lib/plugins:/usr/
opt/mozilla/lib/plugins:/usr/lib/
opt/mozilla/lib/plugins:/usr/lib/mozilla/
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-wmp.xpt
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-qt.xpt
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-gmp.so
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-rm.so
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-gmp.xpt
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in.xpt
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-wmp.so
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-dvx.so
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-qt.so
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in.so
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-rm.xpt
opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins/mplayerplug-in-dvx.xpt
usr/
usr/lib/
usr/lib/mozilla/
usr/lib/mozilla/plugins/
If you don't get around to it by like tomorrow, I can take care of it.