xulrunner install identical copies of libmozjs.so, libxpcom.so and libxul.so under both /usr/lib/xulrunner-1.9.2 and /usr/lib/xulrunner-devel-1.9.2/sdk/lib, coming to about 24 MB in size. /usr/lib/xulrunner-devel-1.9.2 mostly consists of symlinks to /usr/lib/xulrunner-1.9.2, so it seems like it'd be consistent to make those libs under xulrunner-devel-1.9.2/sdk/lib symlinks too, and definitely more efficient... I noticed this quite a while ago, so it's not something which has been introduced in recent ebuilds or anything. Reproducible: Always
Seeing this too.
Also applicable to xulrunner-2.0_beta9_pre-r2 in mozilla overlay.
As most distros bundle the runtime and devel package seperately this was best solution for upstream, if you think of xulrunner ebuild as providing both packages you have the same results of any other distro. TAR_CREATE_FLAGS = -cvhf for reference to code to follow # SDK directory is the libs + a bunch of symlinks $(NSINSTALL) -D $(DESTDIR)$(sdkdir)/sdk/lib if test -f $(DIST)/include/xpcom-config.h; then \ $(SYSINSTALL) $(IFLAGS1) $(DIST)/include/xpcom-config.h $(DESTDIR)$(sdkdir); \ fi (cd $(DIST)/sdk/lib && tar $(TAR_CREATE_FLAGS) - .) | (cd $(DESTDIR)$(sdkdir)/sdk/lib && tar -xf -) $(RM) -f $(DESTDIR)$(sdkdir)/lib $(DESTDIR)$(sdkdir)/bin $(DESTDIR)$(sdkdir)/include $(DESTDIR)$(sdkdir)/include $(DESTDIR)$(sdkdir)/sdk/idl $(DESTDIR)$(sdkdir)/idl ln -s $(sdkdir)/sdk/lib $(DESTDIR)$(sdkdir)/lib ln -s $(installdir) $(DESTDIR)$(sdkdir)/bin ln -s $(includedir) $(DESTDIR)$(sdkdir)/include ln -s $(idldir) $(DESTDIR)$(sdkdir)/idl Hope this helps you all understand more about the build approaches we are using upstream.
