mozilla-gtk2. Teach galeon2 to use these new files. Note, any other app
that depends on these files not having the optional -devel suffix will
need to be re-educated as well.
Remove installing of Xft1 from XFree86-4-libraries, and add dependencies
to the Xft port by all the ports that use it along with whatever patches are
necessary.
Approved by: portmgr (kris), marcus
Also, mark the port as BROKEN if WITH_CALENDAR is defined and
WITHOUT_COMPOSER or WITHOUT_MAILNEWS are also defined. Calendar requires
Composer and Mailnews support.
Mozilla 1.3a. This should fix the calendar build. Note, it will take
some time for the FTP mirrors to catch up with this new tarball.
Reported by: Larry Rosenman <ler@lerctr.org>
* Re-enable optimizations [1]
* Disable JavaScript debugger by default [1]
Acknowledgement goes to the Phoenix port and alane for a patch that
corrects a crash when downloads complete.
Suggested by: David Schultz <dschultz@uclink.Berkeley.EDU> [1]
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
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.
