Thanks for the clarification Carsten! I guess I will have to package my
extension twice then, separately for both iceweasel and icedove.
Fortunately, AFAICS the user experience is not damaged.
It would be nice (for me) if this bug remains open so that people do not
forget this is an *unsolved*
tags 688438 wontfix
thanks
Hello Ximin,
Am 11.11.2012 09:37, schrieb Ximin Luo:
Thanks for the clarification Carsten! I guess I will have to package my
extension twice then, separately for both iceweasel and icedove.
Fortunately, AFAICS the user experience is not damaged.
:)
Yes, but this
Hello Ximin,
Am 04.11.2012 15:23, schrieb Ximin Luo:
Could you elaborate? I was under the impression that (e.g.) icedove version X
and iceweasel version X, both build against the same xulrunner, at version X.
Unfortunately not. The sources of both application bring there own
version for
On 30/10/12 19:50, Carsten Schoenert wrote:
Severity: wishlist
thanks
Hello Ximin,
as you wrote there are two different libxul.so files. That's correct.
One under /usr/lib/icedove/ for Icedove and the other one in
/usr/lib/xulrunner-[ver]/ for Iceweasel.
The reason for this are
Severity: wishlist
thanks
Hello Ximin,
as you wrote there are two different libxul.so files. That's correct.
One under /usr/lib/icedove/ for Icedove and the other one in
/usr/lib/xulrunner-[ver]/ for Iceweasel.
The reason for this are different needings for this librarys. Icedove
don't use the
Package: icedove
Version: 10.0.6-2
Severity: important
Some extensions, such as xul-ext-gnome-keyring[1], work with both iceweasel
and icedove, but are also binary extensions that must be recompiled with each
version of xulrunner that is released. Currently iceweasel and icedove each
package
6 matches
Mail list logo
