In general plugins and native extensions should use these link options. There are two kind of glues to escape this:ĭependent Glue - only for components/modules that get loaded into an already booted libxul application. Xulrunner doesn't support directly linking to its libraries. The upstream guide on how to migrate the code is available here. Xulrunner 1.9 finally enforces frozen linkage. Plugins directory considered by firefox (>= 3)Įxtension directory considered by firefox (>= 3) If they require nspr/nss they should also depend on the libnspr4-dev and libnss3-dev packages. Packages that need the xulrunner 1.9 sdk need to build depend on xulrunner-1.9-dev. So manually add a dependency on xulrunner-1.9 to your package. Xulrunner isn't a real lib, but rather a SDK with a runtime/runner and so the Depends are not auto-detected. ship suite-runnner (seamonkey) 2.0: this isn't mandatory as seamonkey is not in main.ship thunderbird 3.0: this isn't mandatory as it might not be doable and thunderbird should be supportable more easily security wise.Its important to note that as many packages as possible should be transitioned to use xulrunner-1.9, as the security support of 1.8 will eventually cease during the hardy lifetime. use xulrunner 1.8 (which we will keep unsupported in universe).migrate to build against xulrunner-1.9 (preferred) or.rdepends transition in universe: all packages either have to.This includes firefox plugins, gecko embedders and extensions with native components. rdepends transition in main: all packages in main that currently use firefox for gecko or xpcom need to be migrated to use xulrunner-1.9.ship firefox 3.0 with -enable-system-xul: use xulrunner 1.9 instead of the in source libxul for firefox.ship xulrunner 1.9 in main: Shipping xulrunner 1.9 in main is an essential requirement for replacing firefox 2 as the default gecko/xpcom provider in ubuntu.The last two sections annotate patches for real life transitions. This document outlines the release goals and document basics on how to transition your software to xulrunner 1.9. Those shipped in main need to use xulrunner 1.9, universe extensions and plugins can choose. The same is true for extensions and plugins. Gecko embedders in universe can choose to either use xulrunner 1.9 or xulrunner 1.8, but should be aware that xulrunner 1.8 security support will eventually cease during hardy life-cycle - a LTS release. For hardy, every application in main that currently uses firefox as a gecko provider needs to be migrated to use xulrunner 1.9. Xulrunner 1.9 will be the default gecko provider in ubuntu. Transition example - Dependent Glue/Plugin - totem.Transition example - Standalone Glue/Application - yelp.Transition to Xulrunner 1.9 - Instructions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |