ports/121787: when devel/icu is installed, openoffice fails to build

[Mikhail Teterin]

The following reply was made to PR ports/121787; it has been noted by GNATS.

From: Mikhail Teterin <mi+mill at aldan.algebra.com>
To: bug-followup at freebsd.org,
 kvedulv at kvedulv.de
Cc:  
Subject: Re: ports/121787: when devel/icu is installed, openoffice fails to build
Date: Mon, 17 Mar 2008 12:17:39 -0400

 According to the ICU project, OpenOffice is using ICU incorrectly. An issue is 
 reported in:
 
  http://bugs.icu-project.org/trac/ticket/5498
 
 and the proposed fix is in the OOO's database:
 
  http://www.openoffice.org/issues/show_bug.cgi?id=81519 (fixed on Feb 13)
 
 Another issue is OOo flat-out refusal to use icu-3.8 -- it should be more 
 accepting.
 
 I do agree, that our OOo port must be fixed to use /ALL/ of the already 
 installed components (--with-system-foo), instead of building its own 
 versions. In addition to ICU, this list includes, but is not limited to the 
 following (sorted by portname):
 
  * graphics/agg
  * shells/bash
  * x11-fonts/bitstream-vera
  * java/bsh
  * devel/bison
  * devel/boost
  * ftp/curl
  * databases/db42
  * devel/dmake
  * textproc/expat2
  * print/freetype (already an option -- should be default)
  * devel/icu
  * graphics/jpeg
  * www/firefox (or some other mozilla browser)
  * archives/libmspack
  * audio/libsndfile
  * textproc/libtextcat
  * textproc/libwpd
  * textproc/libxslt
  * www/neon
  * devel/nss and nspr
  * lang/python
  * graphics/sane-backends
  * databases/unixODBC
  * archivers/unzip
  * graphics/vigra
  * security/xmlsec1
  * textproc/xt
  * archivers/zip
 
 I'm sure, I missed some... As things stand, OOo builds its own (outdated) 
 versions of the above causing hugely inflated disk-space and build-time 
 requirements. They also end up not using the patches and development/porting 
 efforts of the maintainers of all those ports keeping the already fixed 
 bugs... Heck -- the OOo ports will download/build an entire ancient 
 Mozilla-1.7.5, if you aren't careful!
 
 This is in dramatic contrast to what all the rest of the ports in the tree are 
 doing and speaks poorly of the port's maintainership, frankly. They follow 
 the "vendor's" broken model of bundling everything a bit too literally.
 
 It used to be even worse -- OOo ports used to build THEIR OWN GCC (see the 
 still-present lang/gcc-ooo), but that non-sense appears over...
 
 OOo needs some serious patching to not even extract the "3rd party" 
 components, and to force the OOo's build to use the already installed stuff.
 
 This PR is about OOo, not ICU. I'll reassign it. Yours,
 
  -mi