* Add i18n support [1]
* Don't delete lib/browser_plugins if it was installed by another instance
of Mozilla [2]
PR: 73841 [1]
Submitted by: Jose M Rodriguez <josemi@freebsd.jazztel.es> [1]
ahze [2]
This release notes detailing all of the new goodies in GNOME 2.8 can
be found at http://www.gnome.org/start/2.8/notes/, and the list of what
was fixed in GNOME 2.8.1 can be found at
http://lists.gnome.org/archives/gnome-announce-list/2004-October/msg00056.html.
This release, as well as all of our others, would not have been possible
without the great efforts of our FreeBSD GNOME Team. The list of
current members can be found at http://www.freebsd.org/gnome/contact.html
(including our newest member, Michael Johnson <ahze@FreeBSD.org>).
Special thanks also goes out to all of the loyal FreeBSD GNOME users that
put up with crashes and hangs to test and debug GNOME on FreeBSD. We would
especially like to thank those users that provided patches for GNOME 2.7 and
2.8:
Franz Klammer <klammer@webonaut.com>
Piotr Smyrak <piotr.smyrak@heron.pl>
Radek Kozlowski <radek@raadradd.com>
Khairil Yusof <kaeru@pd.jaring.my>
Yasuda Keisuke <kysd@po.harenet.ne.jp>
Tom McLaughlin <tmclaugh@sdf.lonestar.org>
Vladimir Grebenschikov <vova@fbsd.ru>
GNOME 2.8 also features a new, FreeBSD-specific splashscreen that
was designed by jimmac for GNOME 2.8, then daemonized by
Franz Klammer <klammer@webonaut.com> and Radek Kozlowski
<radek@raadradd.com>.
As with GNOME 2.6, you cannot just "portupgrade" to GNOME 2.8. There is
a script provided at http://www.marcuscom.com/downloads/gnome_upgrade28.sh
that will aid in the upgrade process. Full documentation on the GNOME 2.8
upgrade is coming following this commit.
From all of us at FreeBSD GNOME, ENJOY!
* Build the chrome and component registries in a pkg-install script so that
the resulting paths are correct [1]
For a list of all the changes in 1.7, see
http://www.mozilla.org/releases/mozilla1.7. This port features support for
the GSSAPI extension as well as optional gnome-vfs support.
PR: 65590 [1]
Submitted by: thierry [1]
* Allow one to override JPI_LIST
* Fix some potential lock-ups related to esound
* Fix some potential pthread problems
* Fix libiconv support
* Use built-in libical
* Use included libart_lgpl
* Use SIZE
* Add new CLI options to mozilla startup script [1]
* Make XMLTerm optional [2]
* Don't accidentally include mozilla in the plist twice [3]
PR: 55412 [1]
55330 [2]
56210 [3]
Submitted by: bland [1] [2]
* mozilla-*vendor ports (currently for Mozilla 1.0.1)
* mozilla* ports (currently for Mozilla 1.1)
* mozilla-*devel ports (currently for Mozilla 1.2b)
Special thanks goes to trevor for auto-generating plist patches, cy for
pointing out that the Mozilla startup scripts need to be tailored for
each version of Mozilla, grog for suggesting that some verbage needs to
be added to explain the Java plugin messages at startup, and John
Merryweather Cooper for suggesting a common plugin directory. Of course,
thanks also goes to the user community for suggestions and support.
These ports offer:
* Complete coexistence with each other
* A universal ${PREFIX}/lib/browser_plugins directory
* Auto-generated plists for ease of maintenance
* More accurate pkg-descr's
* A pkg-message pointing users to java/jdk13 for the Java plugin
PR: 42870 42941
Reviewed by: ports gnome
NOTE: mozilla-*-devel is now Mozilla 1.1. mozilla-* (without the -devel) is
back to Mozilla 1.0. mozilla.org states that 1.1 is their new bleeding edge
release, and 1.0 is still the stable release. The release cycle diagram also
indicates that a Mozilla 1.0.1 is coming.
For all users that upgraded from Mozilla 1.0 to 1.1, be aware that running
a blind portupgrade on mozilla will give you mozilla-1.0! If you want to
keep Mozilla 1.1, you will have to change the origin of you mozilla ports to
point to their -devel counterparts.
The -devel ports will install files into -devel directories. Therefore,
both mozilla and mozilla-devel can coexist.
released tarball without version bump. The diff between old and new version
didn'y revealed anything that might be worth PORTREVISION bump.
Submitted by: Mark Knight <markk@knigma.org>, kris
request to enable chatzilla, therefore it is not enabled now - the issue
is under investigation, but anybody is free to smash maintainers with a
relevant patch.
backwards.
This may still not work on 4-stable, but see -hackers,
<200101110441.f0B4fe008116@wartch.sapros.com> for the reason.
Also, I've not yet managed to look into getting the PSM code to build, but
I'm updating this now, before more people send patches.
Submitted by: reg, sobomax, Yoichi ASAI <yatt@msc.biglobe.ne.jp>
