to crash [1]
* Fix a problem connecting to certain IPv6 sites [2]
* Disable more tests to speed compilation
Submitted by: Alexander N. Kabaev <ak03@gte.com> [1]
Hiroharu Tamaru <tamaru@myn.rcast.u-tokyo.ac.jp> [2]
Obtained from: http://bugzilla.mozilla.org/show_bug.cgi?id=186745 [2]
a problem with starting Mozilla from the KDE dock if another instance of
Mozilla is already running.
Tested by: Vivek Khera <vivek@khera.org>
Approved by: portmgr (kris)
new Mozilla instance each time, check to see if one already exists, and if
so, spawn a new browser tab in the current window.
PR: 45610
Submitted by: Nick Jennings
* 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.
* 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)
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.
more acceptable to mozilla.org. Hopefully these will make it into 0.9.9.
Add a hack to minimise the number of files extracted.
Merge in the patches from the mozilla+ipv6 port.
Submitted by: sumikawa (mozilla+ipv6)
based on mozilla-embedded (galeon, skipstone etc.);
- remove commented out line from unixcharset.properties;
- add few `@unexec rm -f' into mozilla-embedded plist to ensure complete
removal of package even if the port based on mozilla-embedded was executed
with root privileges (mozilla has a bad habit of updating files in
${PREFIX}/lib/mozilla* wherever it's possible).
Submitted by: Takashi KANAMARU <kanamaru@sekine-lab.ei.tuat.ac.jp> (Asian langs)
sobomax (the rest)
Submitted by: nsayer
Remove use of libgcc_r, since it was so uncerimoniously removed. If this
doesn't work on -stable, then -stable is broken, and someone needs to fix
it...
Submitted by: Roman Shterenzon <roman@xpert.com>
Use sched_getpriority_max(), instead of hard coded value.
Submitted by: Peter Haight <peterh@sapros.com>, dufault
Revise pkg-comment and pkg-descr.
PR: 24296
Submitted by: roam
Enable SVG support, and disable C++ exceptions (since they will only slow
things down).
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>
