[ Alexander Sack <email address hidden> ]
* Fix: LP #246775 - "wrong user-agent string in hardy build" by adding proper
build-depends
- update debian/control
* Fix: LP #240880 - Remove "previously known as" paragraph
- update debian/control
* webbrowser-3.0-branding split using the awesome branding (LP: #263938)
+ we add a new .desktop file to the source and teach the debian/rules
code about it
- add debian/webbrowser-3.0.desktop
- update debian/rules
+ we magically run config.status on just the Makefiles of our branding
in the binary-install/webbrowser-3.0-branding target
- update debian/rules
+ we introduce a firefox-3.0-branding package as well as an
webbrowser-3.0-branding package in control; webbrowser-3.0-branding
conflicts firefox-3.0-branding, while firefox-3.0 depends on
firefox-3.0-branding | webbrowser-3.0-branding; we update the firefox
meta package to depend on the firefox-3.0-branding; we add a new
metapackage "webbrowser" that tracks the stable webbrowser branch, just
like firefox, but with the difference that it depends on
webbrower-3.0-branding package
- update debian/control
+ higher mozilla-devscripts bar to 0.10 to reflect that we need that
version to properly produce awesome-browser branded original tarballs
- update debian/control
+ patch browser/installer packages-static file to install awesome-browser
content and locale bits
- add debian/patches/awesome_browser_branding_install.patch
- update debian/patches/series
+ patch firefox to ship branding chrome bits in separate jar files.
- debian/patches/browser_branding.patch
- debian/patches/series
+ install firefox branding bits to the firefox-3.0-branding package
and remove them from the firefox-3.0 package so that we ship the awesome
browser chrome by default; in turn we fix that not all awesome branding
bits were available by doing a full make install
DESTDIR=debian/tmp-awesome.
- update debian/rules
- update debian/firefox-3.0.install
+ dpkg-divert non-chrome branding bits; add firefox-3.0-branding.preinst.in
and firefox-3.0-branding.postrm.in maintainer script templates and
register them for substitution in debian/rules; for chrome the trick is
to not divert the whole branding, but just disable the
awesome-browser.manifest when the firefox-3.0-branding package gets
installed; doing so disables the locales override and unhooks the
awesome branding in a way that the offcial branding will take over. We
also try to cleanup diverts that have disappeared during upgrade in
old-postrm of the branding package; this is required to properly cleanup
during major firefox version upgrades - where pkglibdir changes.
- add debian/firefox-3.0-branding.postrm.in
- add debian/firefox-3.0-branding.preinst.in
- update debian/rules
+ introduce rules variable APP_NAME_OTHER, which is used as a placeholder
for awesome-browser
- update debian/rules
+ special case when \"Web Browser\" is found
to be shortBrandName. In that case we use /usr/bin/webbrowser as
exePath in nsGNOMEShellService (for settin default browser)
- update debian/patches/lp185622_system_path_default_browser.patch
+ ship /usr/bin/webbrowser and /usr/bin/webbrowser-3.0 links in
firefox-3.0 package
- update debian/firefox-3.0.links
+ ship awesome branding in webbrowser-3.0-branding package
- update debian/rules
[ Fabien Tassin ]
* Drop more firefox-3.0 references to ease merge with the 3.1 branch
- update debian/rules
* Fix buffer overflow in realpath() at runtime and drop -U_FORTIFY_SOURCE
from CPPFLAGS (LP: #263014)
- add debian/patches/bz412610_att335369_realpath_overflow.patch
- update debian/patches/series
This bug was fixed in the package firefox-3.0 - 3.0.2+build3+ nobinonly- 0ubuntu1
--------------- build3+ nobinonly- 0ubuntu1) intrepid; urgency=low
firefox-3.0 (3.0.2+
[ Alexander Sack <email address hidden> ] 3.0-branding split using the awesome branding (LP: #263938) webbrowser- 3.0.desktop install/ webbrowser- 3.0-branding target 3.0-branding package as well as an r-3.0-branding package in control; webbrowser- 3.0-branding 3.0-branding, while firefox-3.0 depends on 3.0-branding | webbrowser- 3.0-branding; we update the firefox 3.0-branding; we add a new -3.0-branding package patches/ awesome_ browser_ branding_ install. patch patches/ series patches/ browser_ branding. patch patches/ series 3.0-branding package debian/ tmp-awesome. firefox- 3.0.install 3.0-branding. preinst. in 3.0-branding. postrm. in maintainer script templates and browser. manifest when the firefox- 3.0-branding package gets firefox- 3.0-branding. postrm. in firefox- 3.0-branding. preinst. in patches/ lp185622_ system_ path_default_ browser. patch webbrowser- 3.0 links in firefox- 3.0.links 3.0-branding package
* Fix: LP #246775 - "wrong user-agent string in hardy build" by adding proper
build-depends
- update debian/control
* Fix: LP #240880 - Remove "previously known as" paragraph
- update debian/control
* webbrowser-
+ we add a new .desktop file to the source and teach the debian/rules
code about it
- add debian/
- update debian/rules
+ we magically run config.status on just the Makefiles of our branding
in the binary-
- update debian/rules
+ we introduce a firefox-
webbrowse
conflicts firefox-
firefox-
meta package to depend on the firefox-
metapackage "webbrowser" that tracks the stable webbrowser branch, just
like firefox, but with the difference that it depends on
webbrower
- update debian/control
+ higher mozilla-devscripts bar to 0.10 to reflect that we need that
version to properly produce awesome-browser branded original tarballs
- update debian/control
+ patch browser/installer packages-static file to install awesome-browser
content and locale bits
- add debian/
- update debian/
+ patch firefox to ship branding chrome bits in separate jar files.
- debian/
- debian/
+ install firefox branding bits to the firefox-
and remove them from the firefox-3.0 package so that we ship the awesome
browser chrome by default; in turn we fix that not all awesome branding
bits were available by doing a full make install
DESTDIR=
- update debian/rules
- update debian/
+ dpkg-divert non-chrome branding bits; add firefox-
and firefox-
register them for substitution in debian/rules; for chrome the trick is
to not divert the whole branding, but just disable the
awesome-
installed; doing so disables the locales override and unhooks the
awesome branding in a way that the offcial branding will take over. We
also try to cleanup diverts that have disappeared during upgrade in
old-postrm of the branding package; this is required to properly cleanup
during major firefox version upgrades - where pkglibdir changes.
- add debian/
- add debian/
- update debian/rules
+ introduce rules variable APP_NAME_OTHER, which is used as a placeholder
for awesome-browser
- update debian/rules
+ special case when \"Web Browser\" is found
to be shortBrandName. In that case we use /usr/bin/webbrowser as
exePath in nsGNOMEShellService (for settin default browser)
- update debian/
+ ship /usr/bin/webbrowser and /usr/bin/
firefox-3.0 package
- update debian/
+ ship awesome branding in webbrowser-
- update debian/rules
[ Fabien Tassin ] patches/ bz412610_ att335369_ realpath_ overflow. patch patches/ series
* Drop more firefox-3.0 references to ease merge with the 3.1 branch
- update debian/rules
* Fix buffer overflow in realpath() at runtime and drop -U_FORTIFY_SOURCE
from CPPFLAGS (LP: #263014)
- add debian/
- update debian/
-- Alexander Sack <email address hidden> Tue, 02 Sep 2008 11:59:53 +0200