on the whole gstreamer gang which are only uses by web browsers to
display audio/video.
So remove RUN_DEPENDS, it'll be explicitely added to webkit browsers
with a small comment so that maintainers of such browsers can decide
which gstreamer dependencies they need/want.
ok landry@ (maintainer)
* Fixes some issues in the admin area where some older browsers (IE7,
in particular) may slow down, lag, or freeze.
* Fixes the use of multiple trackback URLs in a post.
Prevents improperly sized images from being uploaded as headers from
the customizer.
* Ensures proper error messages can be shown to PHP4 installs.
(WordPress requires PHP 5.2.4 or later.)
* Fixes handling of oEmbed providers that only return XML responses.
* Addresses pagination problems with some category permalink
structures.
* Adds more fields to be returned from the XML-RPC wp.getPost method.
* Avoids errors when updating automatically from very old versions of
WordPress (pre-3.0).
* Fixes problems with the visual editor when working with captions.
Tested on i386.
Ok merdely@
ports, for the ports that are built both on ruby 1.8 and ruby 1.9,
switch the category Makefiles to explicitly list the ruby18 FLAVOR
instead of the ruby19 FLAVOR.
Also, for home_run, fastri, and fastercsv, explicitly build only the
ruby 1.8 version of the port. These libraries can run on ruby 1.9, but
it doesn't make sense to build a ruby 1.9 version by default.
FLAVOR and FLAVORS set to ruby18, so attempting to build them without a
FLAVOR set still builds the ruby 1.8 version.
Remove MAINTAINER at his request.
- remove useless patch to gfx/thebes/Makefile.in adding -lpangox-1.0 to
EXTRA_DSO_LDOPTS, this was maybe useful before ffx 3.0, but mozilla
stopped using pangox between 2.0 and 3.0. See for the last traces of
pangox.h use : https://bugzilla.mozilla.org/show_bug.cgi?id=528941. See
also bugs #323671/#338446
- backport the patch from #528941 to remove useless pangox.h inclusion
from www/firefox35.
- remove the RUN_DEPENDS on pangox-compat
- bump all corresponding REVISIONS
- while here, make sure all moz ports depend on latest nspr 4.9.2 since
it'll be a requirement for upcoming gecko 16 releases
The situation is this: even when we --disable-gtk-doc, if gtk-doc is
actually installed at configure stage, tools like gtkdoc-rebase will be
picked up and run during the install target. That is bad because the
gtk-doc package may have been removed by then, especially during dpb(1)
bulks (we explicitely disable support for it so why should it stay...).
So for now, let's add the following env to configure whenever we use
--disable-gtk-doc, until a bettersolution is found...
CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \
ac_cv_path_GTKDOC_REBASE="" \
ac_cv_path_GTKDOC_MKPDF=""
* Unbreak custom URI handling
* Fix display of about:favorites with no favorites
* Prevent using back on an about:secviolation page from returning back
to the exact same page that triggered the cert warning.
* Fix build with glib 2.30.0
* Kill a crash when using older libsoup versions
* Sync the preloaded HSTS list with Chromium's
Tested on amd64.
Ok kili@
- allow multiple AddHeader directives
- fixed memory leak in config/AddHeader
- fixed memory leak in DH
- fixed problem in SNI certificate storage
- changed long to long long for support of requests larger than 2GB
- added parsing for certificate CN
- fixed problem in task enqueing
- fixed small problem in Makefile
And others, while here, GROFF is not needed and patches applied
upstream.
Ok 'Looks fine' aja@
