=== stevel_ is now known as stevel
=== stevel_ is now known as stevel
[14:26] <stefanlsd> Does anyone have an example of an extentsion that shows how an extension is installed. I have a rules file that builds the extension, i just need to incorporate the right xpi.mk in now
[16:30] <stefanlsd> Anyone around to help with some extension packaging questions?
[17:33] <mitchell1> hello
[17:34] <mitchell1> how can I change the language of shiretoko to spanish?
[17:34] <mitchell1> in intrepid
[19:21] <Jazzva_> stefanlsd: Regarding packaging an extension, this might help https://wiki.ubuntu.com/MozillaTeam/Extensions/Packaging
[19:29] <stefanlsd> Jazzva_: yeah. thanks. i've seen that. still got some questions tho
[19:30] <Jazzva_> stefanlsd: hmm, it should use xpi.mk provided by mozilla-devscripts package.
[19:31] <Jazzva_> stefanlsd: what do you mean when you say "to incorporate the right xpi.mk"?
[19:33] <stefanlsd> Jazzva_: in this case, i use a debian rules with targets to build the xpi. if i include the xpi.mk it conflicts since xpi.mk has its own rules. ie. conflicts as there are 2 clean rules. i think what i want is an example of something similar. unless i've gone about it the wrong way?
[19:37] <Jazzva_> stefanlsd: I guess you can modify xpi.mk if you really need to. But in most cases, it should be sufficient to edit MOZ_XPI_BUILD_COMMAND in debian/rules template provided by XPI.TEMPLATE. If you downloaded the extension as a xpi file, you should use med-xpi-unpack script (provided by mozilla-devscripts) to unpack the xpi file, add debian/ dir, edit template files in it, and xpi.mk will call med-xpi-pack for you when you run
[19:37] <Jazzva_>  debuild.
[19:38] <Jazzva_> stefanlsd: so, in most cases you don't need to add your own targets to debian/rules (that is, if you use mozilla-devscripts)
[19:41] <stefanlsd> Jazzva_: this is google gears. so I build it from source and get an .xpi for the correct architecture. im just not sure how i call the rest to take that resulting xpi and install it.   i agree it would be easier if i just used the xpi and the xpi.mk include.  so i think i just need a similar example where the build results in a xpi and the xpi gets installed. (i hope im making sense)
[19:43] <Jazzva_> stefanlsd: then just specify that command, which you use to produce a xpi file, in MOZ_XPI_BUILD_COMMAND in debian/rules template.  once you run debuild, it will call that command, produce a xpi file, and then do the rest of installation. At the end, you'll get a deb file.
[19:45] <stefanlsd> Jazzva_: aah ok. let me try that. i see they often link that to a sh script that does the build
[19:47] <Jazzva_> stefanlsd: yes, just replace it with the command, which you call to produce a xpi file
[19:48] <stefanlsd> Jazzva_: k. thanks. i had it all building with the debian/rules. need to see if i can change that.  was using quilt for patching
[19:51] <Jazzva_> stefanlsd: no problem, good luck.
[21:06] <stefanlsd> What should happen with i create a deb with xpi.mk and install it.  I dont seem to get the extension in firefox. Do i need to do anything else?
[21:11] <stefanlsd> oh, i got it.  it does work. firefox wasnt closing properly :)
[23:19] <mitchell> hello all, i would like to know if there is a way to have the firefox 3.5 GUI in spanish
=== asac_ is now known as asac
[23:35] <mitchell> i would like to know if there is a way to have the firefox 3.5 GUI in spanish, can someone please help?