On 15.12.2012 04:06, Michael Biebl wrote:
> How does this exactly work? How does the iceweasel extension know that
> it should load libgnomekeyring.so whereas the icedove extension should
> load libgnomekeyring-icedove.so?
nvm, found it in the mean time: the chrome.manifest maps the libraries
to
Hi again,
On 15.12.2012 04:06, Michael Biebl wrote:
Hi Ximin,
I'm mostly interested in this change in 0.6.6-1:
* Build separate libraries against both xulrunner-dev and
icedove-dev. (Closes: #690324)
So I can rebuild the extension for iceweasel/icedove 7.
Hi Ximin,
I'm mostly interested in this change in 0.6.6-1:
* Build separate libraries against both xulrunner-dev and
icedove-dev. (Closes: #690324)
So I can rebuild the extension for iceweasel/icedove 7.
I see that the package now builds
/usr/lib/xul-ext/gnome-keyring/platform/Linux_x86_6
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "mozilla-gnome-keyring"
* Package name: mozilla-gnome-keyring
Version : 0.6.5-1
This is an update to an already existing package:
http://packages.debian.org/source/experimenta
4 matches
Mail list logo