11:10 flo 

- Remove www/libxul19, is has been vulnerable and unsupported upstream for
  quite some time.
- Switch all remaining consumers to depend on www/libxul
- Mark ports that don't work with the new libxul BROKEN
- Mark some old ports DEPRECATED with a reasonable timeout

Approved by:	portmgr (miwi)

 

19:19 beat 

- Move libxul 1.9.2 to www/libxul19
- Update www/libxul to 10.0.7
- Update all dependent ports to use www/libxul19 (no functional changes)
- Bump PORTREVISION on ports where libxul is a run dependency as the
  resulting package will change.

Submitted by:	Jan Beich <jbeich@tormail.org>
With hat:	gecko

 

20:39 crees 

Reset maintainership

PR:             ports/164871
Submitted by:   Jonathan Chen <jonc@chen.org.nz> (maintainer)

20:09 beat 

- Replace custom Firefox dependency lines with USE_FIREFOX_BUILD

Approved by:    Jonathan Chen <jonc AT chen.org.nz> (maintainer)

00:55 pgollucci 

- Account for ports/150327
  Do not install meta data (META-INF) since its not needed
  allow for xpi-post-extract to still work in xpi-* ports

   o fix pkg-plist
   o fix XPI_DIRS, XPI_FILES
   o Bump PORTREVISION
   o s/post-extract/xpi-post-extract/

PR:             ports/150327
Submitted by:   Lapo Luchini <lapo@lapo.it>, tweaked by myself
Approved by:    maintainer timeout (miwi)
Tested by:      P6 TB Run, RideCharge Inc. / Taximagic TB Run

08:56 beat 

- Bump PORTREVISION after libxul update

PR:             ports/149044
Expr-run by:    pav@
Approved by:    portmgr (pav)

06:47 dinoex 

- update to 1.4.1
Reviewed by:    exp8 run on pointyhat
Supported by:   miwi

06:09 linimon 

Mark as only for amd64/i386: coredumps on sparc64, and not yet tested
elsewhere.

Hat:            portmgr

22:30 miwi 

- Add support for i386

PR:             143299
Submitted by:   Jonathan Chen <jonc@chen.org.nz> (maintainer)

13:09 miwi 

The GWT developer plugin spans the gap between Java bytecode in the
debugger and the browser's JavaScript. There's no compiling of code to
JavaScript to view it in the browser. You can use the same edit-refresh-view
cycle you're used to with JavaScript, while at the same time inspect
variables, set breakpoints, and utilize all the other debugger tools
available to you with Java. And because GWT's development mode is now
in the browser itself, you can use tools like Firebug and Inspector
as you code in Java.

PR:             ports/143042
Submitted by:   Jonathan Chen <jonc at chen.org.nz>