to do this). This feature will be used for the upcoming Galeon 1.3.0
port. [1]
* Allow users to disable Composer (define WITHOUT_COMPOSER to do this) [2]
Submitted by: David Magda <dmagda@magda.ca> [2]
Obtained from: Galeon 1.3.0 tarball (with some modification) [1]
* Fix a problem with plugins not actually loading
* Hopefully correct some issues with installs erroring out with Error 1
* Conditionalize Xft support (by default it's enabled, but can be disabled
by defined WITHOUT_XFT)
Submitted by: Jung-uk Kim <jkim@niksun.com> [1]
Obtained from: Mozilla's Bugzilla bug 174989 [1]
* 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
Indicate that the mozilla port reflects the most stable venor (or API) release,
while the -devel port is the latest official release of Mozilla.
PR: 42706
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.
* Silence a portlint nit wrt to the order of PORTREVISION in the Makefile
* Don't use --enable-reorder on non-i386 archs
* Mark BROKEN for now on alpha as there is still a core dump during
post-build
* Use USE_GNOMENG
Submitted by: Peter Kostouros <kpeter@melbpc.org.au> (patch for -CURRENT)
me (everything else)
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
segmentation fault after the initial patch was applied.
See http://sec.greymagic.com/adv/gm001-ns/ for more details on the
vulnerability.
Obtained from: Mozilla's Bugzilla database (bugs 141061 and 137644)
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.
