FS#9004 - mozilla-common 1.1-2 doesn't reflect the change folder for mozilla packages.

Attached to Project: Arch Linux
Opened by Baeyens (berbae) - Saturday, 22 December 2007, 22:10 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 13:58 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Alexander Baldeck (kth5)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: mozilla-common 1.1-2 in Testing is the same as mozilla-common 1.1-2 in Extra

Details :It seems that the package in Testing should reflect the change from /opt/mozilla to /usr/lib/mozilla in the mozilla-common.sh script :

export PATH="${PATH}:/usr/lib/mozilla/bin"
export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/usr/lib/mozilla/lib/pkgconfig"
export MOZ_PLUGIN_PATH="/usr/lib/mozilla/plugins"

rather than :

export PATH="${PATH}:/opt/mozilla/bin"
export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/opt/mozilla/lib/pkgconfig"
export MOZ_PLUGIN_PATH="/opt/mozilla/lib/plugins:/usr/lib/mozilla/plugins"

It seems to me an inadvertent error in Testing, a new mozilla-common 1.1-3 package is needed, isn't it ?
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 09 February 2008, 13:58 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Saturday, 22 December 2007, 23:53 GMT
These things are left this way intentionally. The /opt/mozilla/bin prefix will disappear quite soon, so the whole path line can be removed then. Same goes for the pkgconfig path.
The MOZ_PLUGIN_PATH lists both the old location and the new location, so 3rd party plugins keep working. The current mozilla-common package is actually a transition package to keep things working while we're still changing mozilla prefix to /usr.
Comment by Baeyens (berbae) - Sunday, 23 December 2007, 13:40 GMT
Yes I understand that quite well, but I was spoken about the package in the Testing repository where I thought the entire new path line is tested. And I understood that a new mozilla-common package should have been there also.
Is this normal that the mozilla-common package 1.1-2 is present both in Extra and Testing, the same release version ?
That was what bothered me.
Thanks.

Loading...