Firefox ESR is intended for groups who deploy and maintain the desktop
environment in large organizations such as universities and other
schools, county or city governments and businesses. During the extended
cycle, no new features will be added to a Firefox ESR; only
high-risk/high-impact security vulnerabilities or major stability fixes
will be corrected.
Note that using it on OpenBSD is NOT supported by mozilla. People
willing to deploy it should subscribe to the EWG mailing list.
http://www.mozilla.org/en-US/firefox/organizations/faq/
Installs as firefox-esr and doesnt conflict with mainline www/mozilla-firefox.
Learn to use several profiles if you plan to use both.
req'd by several.
from DESCR:
The WWW::Mechanize::GZip module tries to fetch a URL by requesting
gzip-compression from the webserver.
If the response contains a header with 'Content-Encoding: gzip', it
decompresses the response in order to get the original (uncompressed)
content.
This module will help to reduce bandwith fetching webpages, if supported
by the webeserver. If the webserver does not support gzip-compression,
no decompression will be made.
This modules is a direct subclass of WWW::Mechanize and will therefore
support any methods provided by WWW::Mechanize.
The decompression is handled by Compress::Zlib::memGunzip.
There is a small webform, you can instantly test, whether a webserver
supports gzip-compression on a particular URL:
http://www.computerhandlung.de/www-mechanize-gzip.htm
ok sthen@
(it was kept separately because 3.x didn't build on some arch due to an
incomplete atomic ops autoconf check which has since been repaired) and
replace with 3.4 (devel version). Enable additional helpers and turn on
support for rock cache dirs.
got no objection.
The main reason is that they don't add any value (basically an enhanced
tar xzf of upstream's tarball with nothing OpenBSD specific nor added
documentation) and that they are often left unmaintainned and outdated
in the tree which leads people to think they are still maintained while
they really are not.
Discussed with several...
no objection dcoppa@ benoit@ zhuk@
"And they were singing Bye, Bye Wikimedia Pie..." ian@
have become pretty useless nowadays (and the pkg tools do not display
them anyway).
Some which contained valuable information have been turned into READMEs.
ok jasper@ sthen@
input/ok naddy@
There is an updated release which is 4 years old which source is not
easily fetchable, does not work well in chroot... and the only supported
way of fully running that stuff is using the commercial version on linux.
"of course" ok robert@
Changes in 3.7 (http://codex.wordpress.org/Version_3.7):
* Background Updates
* Stronger Password Meter
* Improved Search
* Better Global Support
Changes in 3.7.1 (http://codex.wordpress.org/Version_3.7.1):
* Images with captions no longer appear broken in the visual editor.
* Allow some sites running on old or poorly configured servers to
continue to check for updates from WordPress.org.
* Avoid fatal errors with certain plugins that were incorrectly
calling some WordPress functions too early.
* Fix hierarchical sorting in get_pages(), exclusions in
wp_list_categories(), and in_category() when called with empty
values.
* Fix a warning that may occur in certain setups while performing
a search, and a few other notices.
ok ajacoutot@
