~caine/chromium-browser/duckduckgo : changes

~caine/chromium-browser/duckduckgo » Changes from revision 916

From Revision 916 to 897

Rev	Summary	Authors	Date
916	patches/series patches/series patches/duckduckgo.patch: Add duckduckgo.patch to series and update DuckDuckGo search provider for our major countries.	Caine Tighe	10 years ago
915	patches/duckduckgo.patch: Add DuckDuckGo to the end of the d... patches/duckduckgo.patch: Add DuckDuckGo to the end of the default search engines list in Chromium.	Caine Tighe	10 years ago
914	Update version for release. Update version for release.	Chad Miller	10 years ago
913	debian/keep-alive.sh. Quit if disk environment disappears. debian/keep-alive.sh. Quit if disk environment disappears.	Chad Miller	10 years ago
912	* debian/tests/: * debian/tests/: - Add smoketest to verify that chromium runs. - Add a empty webapps test file for notes about what parts of webapps will or should be tested.	Chad Miller	10 years ago
911	* New release 28.0.1500.71. * New release 28.0.1500.71. - Only one hardware arch builds the independent files, so in our sanity test that we install everything upstream built once and only once in packages, we have to consider whether this build didn't even try to take and use arch-independent files. Don't look for some file paths if we don't use them. (Also, if we match too much of what we used, also remove matches from the list of created. This should be better.)	Chad Miller	10 years ago
910	Make a fall-back for when upstream fails to release a Releas... Make a fall-back for when upstream fails to release a Release. Package up as best we can from source control. debian/rules and debian/checkout-orig-source.mk .	Chad Miller	10 years ago
909	Build reliability and automated-ui tests. We don't use thes... Build reliability and automated-ui tests. We don't use these yet, but we will soon.	Chad Miller	10 years ago
908	More explicitivity in testing things. Document exclusions. More explicitivity in testing things. Document exclusions.	Chad Miller	10 years ago
907	Better comments and better built-files-are-packaged tests. F... Better comments and better built-files-are-packaged tests. FIx a bug in grepping stdin.	Chad Miller	10 years ago
906	Be more explicit about what files we set the rpath on. Get ... Be more explicit about what files we set the rpath on. Get all executables. We missed chromedriver before.	Chad Miller	10 years ago
905	Add more exceptions for packaging contents tests, this time ... Add more exceptions for packaging contents tests, this time to exclude files that are in package but not from the build tree.	Chad Miller	10 years ago
904	EXPERIMENT: Try not stripping enormous libraries' symbols ex... EXPERIMENT: Try not stripping enormous libraries' symbols explicitly.	Chad Miller	10 years ago
903	Clean up rules. Clean up rules.	Chad Miller	10 years ago
902	Clean up changelog. Clean up changelog.	Chad Miller	10 years ago
901	Clean up packaging sanity test that verifies everything we b... Clean up packaging sanity test that verifies everything we build is put into a package.	Chad Miller	10 years ago
900	* debian/chromium-browser.sh.in: * debian/chromium-browser.sh.in: - Detect at startup the features of the CPU that we might be intersted in and export info into the environment. This is step one of a longer workaround for sandbox /proc restrictions.	Chad Miller	10 years ago
899	Build and run unit test suite as part of making a package. A... Build and run unit test suite as part of making a package. Abort if more than 15 out of ~2000 tests fail.	Chad Miller	10 years ago
898	* debian/source/lintian-overrides: * debian/source/lintian-overrides: - Supress warnings about known intentional decisions. Package name, statically linked bundled libraries, setuid root sandbox.	Chad Miller	10 years ago
897	- Return to using no explicity NEON fpu, and instead try to ... - Return to using no explicity NEON fpu, and instead try to detect at runtime NEON caps. This effectively disables NEON, so far. * debian/patches/arm-neon.patch: - Compile in NEON instructions for ARM, even if we can't reliably check for whether our CPU is capable of running them yet. The major problem remaining is that the sandbox security wrapper defeats any test of /proc/cpuinfo .	Chad Miller	10 years ago

Older »