infinity0 / mozilla-gnome-keyring-legacy

A firefox extension that enables Gnome Keyring integration (legacy version)
https://bugzilla.mozilla.org/show_bug.cgi?id=309807
Other
55 stars 8 forks source link

Upload to addons.mozilla.org #14

Open ghost opened 12 years ago

ghost commented 12 years ago

Hi, thanks for keeping this great addon alive. Works fine on Debian testing / Iceweasel 10.0.5esr-1. What about submitting this to addons.mozilla.org? It would be easier to find and install for GNOME-keyring/firefox/iceweasel users, and less error-prone as there are many forks of this project - it seems this one is the most up-to-date.

Let me know if you agree, I will deal with the upload process if you like.

infinity0 commented 12 years ago

I'm happy as long as someone else does the work. :p IIRC the main difficulty with distributing it on AMO is that you must distribute both the x86 and x86-64 binaries in the same XPI, which is annoying. It is possible to make a build script that uses gcc-multilib to build for both architectures using the same machine/OS (which must be x86-64), but it is quite tedious to get this right, especially since you must get both the x86 and x86-64 versions of xulrunner-dev and libgnome-keyring-dev on the same machine.

BTW this extension is already in debian - you can aptitude install xul-ext-gnome-keyring. There are also other maintainers packaging this for other distros. That is why I haven't paid attention to AMO, since GNU/linux distros generally already have their own packaging systems.

ghost commented 11 years ago

Thanks for your reply, please excuse the delay. I've been trying to properly package an XPI with both x86 and x86-64 binaries, unsuccessfully. Unfortunately the xul-ext-gnome-keyring package in experimental is not compatible with Iceweasel 15 (release from http://mozilla.debian.net). This is more the package maintainer's problem, so I guess I will push a Debian bug report. For now i'm stuck with the default Firefox password manager.

Thanks for your work on this addon

infinity0 commented 11 years ago

I am the package maintainer :) The problem stems from the fact that iceweasel and icedove are at different versions in experimental, so even if I recompile a release for iceweasel, that would break compatibility for icedove. I have prodded them about it but I may have to end up releasing two separate binary packages from the same source...