[Pkg-mozext-maintainers] mozilla-devscripts and binary components

Alan Woodland awoodland at debian.org
Fri Sep 18 23:04:14 UTC 2009


Hi,

What's the proper procedure for packages which build binary components
with mozilla-devscripts? I've put together a test bringing
mozilla-traybiff over to pkg-mozext and using mozilla-devscripts, but
it's now placing libtraybiff.so in /usr/share, which is almost
certainly wrong...

What's the 'proper' way to correct this problem with mozilla-devscripts?

debian/rules is very simple now:

!/usr/bin/make -f

MOZ_XPI_BUILD_COMMAND := make MOZILLA_PLATFORM=tbird MOZ_TRUNK=1
components chrome install.rdf && cp debian/chrome.manifest . && zip -r
traybiff.xpi . -i defaults/preferences/tray-biff.js
chrome/tray-biff.jar components/libtraybiff.so
components/libtraybiff.xpt chrome.manifest * -x debian\* -x debian/\*
temp-xpi-\* license.txt Makefile COPYING changelog get-platform
make-install.rdf README \*.in

MOZ_XPI_MOZILLA_DIRS := icedove

include /usr/share/cdbs/1/rules/dpatch.mk
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/mozilla-devscripts/xpi.mk

clean::
	make -k MOZILLA_PLATFORM=tbird MOZ_TRUNK=1 clean
	-rm -f chrome.manifest

(Will be putting this all into git soon too)

Thanks,
Alan



More information about the Pkg-mozext-maintainers mailing list