files. It was originally created for Facebook's Video project
(http://facebook.com/video/) for fast video hinting. It is loosely
based on the Ruby FLVTool2, but is written in C++ for performance
reasons.
WWW: http://mirror.facebook.com/facebook/flvtool++/
PR: ports/126336
Submitted by: Gea-Suan Lin <gslin at gslin dot org>
and scalc (*.sxc) formats.
It doesn't depend on Open Office or any other external tools or libraries.
There are three output modules:
* o3read displays a dump of the parse tree
* o3totxt creates plain text
* o3tohtml creates html code
Example: unzip -p document.odt content.xml | o3totxt
WWW: http://siag.nu/o3read/
PR: ports/126320
Submitted by: Alex Samorukov <samm at os2 dot kiev dot ua>
we should not set GNU_CONFIGURE to yes. Instead, we use HAS_CONFIGURE.
This eliminates the warning below:
configure: warning: ignoring option --build=amd64-portbld-freebsd7.0
Approved by: ehaupt (maintainer via irc)
"Fix" the regression tests by running them as nobody if the regression-test
target is run by root. Remove the .if defined(MAINTAINER_MODE) guards so
the package cluster will run the tests (they pass correctly on i386).
By default, kdepim3 unconditionally require old libopensync,
which lead to conflict with kdepim4 (based on new libopensync,
if enabled)
PR: based on 126669
Reported by: "Dima Panov" <fluffy@fluffy.khv.ru>
Submitted by: Max Brazhnikov (via area51)
order to fix the build failure in graphics/xaralx:
../wxOil/compatdef.h:605: undefined reference to `malloc_usable_size'
(if the library is stripped then nm(1) shows "no symbols")
Submitted by: vd
Reviewed by: pav
Approved by: Pedro Giffuni <pfgshield-freebsd@yahoo.com> (maintainer)
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
Temporarily put the regression-test target under if
defined(MAINTAINER_MODE) because it eats /dev/null if run as root and
the package cluster runs it as root.
* Put deprecation warnings in more places in the docs, and in
the podtohtml script
* Use Pod::Simple::HTML instead of this module
Submitted by: delphij
PR: ports/126690
when the user does not have the OPTION ticked. So remove the part of this
patch that cuts it out unconditionally in favor of the already-existing
sed option in the Makefile.
pointy-hat-collection++
Submitted by: John Marshall <john.marshall@riverwillow.com.au>
