Starting with version 1.3 mpeg4ip-libmp4v2 installs libmp4av that mpeg4ip
previously installed. It is advised to de-install mpeg4ip-libmp4v2 and
mpeg4ip before updating to mpeg4ip-1.3 or mpeg4ip-libmp4v2-1.3. If you
have already updated mpeg4ip-libmp4v2 and mpeg4ip you should deinstall
mpeg4ip and reinstall mpeg4ip-libmp4v2 before updating mpeg4ip.
This does not affect users who just have mpeg4ip-libmp4v2 installed
and not mpeg4ip.
Starting with version 1.3 mpeg4ip-libmp4v2 installs libmp4av that mpeg4ip
previously installed. It is advised to de-install mpeg4ip-libmp4v2 and
mpeg4ip before updating to mpeg4ip-1.3 or mpeg4ip-libmp4v2-1.3. If you
have already updated mpeg4ip-libmp4v2 or mpeg4ip you should reinstall
both mpeg4ip-limp4v2 and mpeg4ip.
- Convert to OPTIONS [1]
- Use %%DATADIR%% [2]
- Add a hint to UPDATING because of changed config file semantics. [1]
Submitted by: maintainer [1],
barner [2]
PR: ports/81375
This release has significant change in API.
All old code *will* broken.
Read how to fix it here: http://perl.apache.org/docs/2.0/rename.html
PR: ports/79962
Submitted by: maintainer
installed, the patched gram.y file would not be used and the security
patch would be a no-op. Also, I've had reports of compilation errors
related to bison.
Since checking for the correct version of bison is hard and error
prone, I'm doing what the postgresql distribution does - patching the
yacc:ed .c file to get rid of the building dependency.
Bumping portrevision of -server.
Pointy hat to: me
Noticed by: Mike Harding and others
Security: http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html
Approved by: seanc (implicit)
http://www.opera.com/linux/changelogs/800/
- Use DATADIR in plist.
- To upgrade, please read in either pkg-descr or UPDATING for detail
- The pkg-descr will be update when opera.com is in less traffic.
- Copy pkg-message in UPDATING. As for www/opera maintainer/committer,
you can just add 'www/opera' when it updates to 8.0.
Over the past several weeks, Tom Lane has been working on replacing
our old Cache Management Alorithm (ARC) with a new, patent free one
(2Q).
In order to reduce the number of 8.x deployments out there that are
using the old manager, we have just released 8.0.2, and encourage
adminstrators to upgrade at their earliest convience.
For those already running 8.x on your production servers, please
note that this upgrade does *NOT* require a dump restore, but due to
a bump in the major version number for the client library (libpq),
it *WILL* require all client applications to be recompiled at the
same time.
For full release info, see
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-2
Apart from the upgrade, three new config options are added:
A patch (experimental) for supporting proper collation
of utf-8 encoded locales, using IBM's ICU package (devel/icu). See
http://people.freebsd.org/~girgen/postgresql-icu/README.html for more
info.
An optional patch written by Evgen Potemkin, which allows
PostgreSQL to make hierarchical queries à la Oracle [1].
An option is added that allows the use of 64 bit ints to
store dates [2].
PR: ports/79165 [1], ports/76999 [2]
Submitted by: Marcos Tischer Vallim [1], Christian Ullrich [2]
Approved by: ade, seanc (implicit)
script. This means that mdnsd is not started by default and must be
enabled by adding an mdnsd_enable="YES" line to your /etc/rc.conf.
This works around a panic in the multicast code when network interfaces
are removed and multicast sockets are open on them since many users of
this port only need the utilities, not the daemon.
Approved by: portmgr (krion)
* SHA-256 has replaced SHA-1 as a hash function used for verifying
integrity of the ports tree.
* The RSA signature verification is now performed using OpenSSL
rather than "borrowing" code from FreeBSD Update.
* In addition to distributing the ports tree, portsnap now also
produces up-to-date INDEX, INDEX-4, and INDEX-5 files.
* When fetching a series of patches, portsnap now prints a simple
progress indicator.
PR: ports/79044
Submitted by: maintainer
- Update boxtools to 0.70.0.
- Update bbpager to 0.4.0.
- Global cleanup in blackbox and bbkeys.
PR: ports/78967
Submitted by: Andrew J. Caines <A.J.Caines@halplant.com>
3.0.0 mostly consists of a more flexable portable gmond which requires a
new config file format. Information about changes in this release can
be found on the website at:
http://ganglia.info/archives/cat_releases.html
and in ports/UPDATING.
${PTHREAD_CFLAGS} and ${PTHREAD_LIBS} include in the build to kill the
headache of old '_r' and can't run with something like ruby-opengl, ruby-sdl,
ruby-gtk2 and etc on FreeBSD 4.x or older 5.x. With this commit should solve
those issues. It is recommend you to rebuild any apps that depend on
lang/ruby18, so see the UPDATING for detail.
Remove the 'BROKEN' on the other ports that knu has added them few weeks ago.
Some of them have been tested, so if one of them is still broke then please
let us know and one of us will re-add the 'BROKEN'.
This changes was worked by lofi and me. lofi did everything on FreeBSD 4.x
and I did others. lofi, thanks for help!
Tested by: many people
Tested on: i386 (FreeBSD 4.x, 5.x and 6.x), amd64 (FreeBSD 5.x and 6.x),
and sparc64 (FreeBSD 5.x and 6.x)
Not test on: ia64 and alpha
Approved by: portmgr (kris)
A lot of tools and macros has been updated and the share/texmf* directory
structure has been changed as well. The portupgrade utility should work,
but please read http://people.freebsd.org/~hrs/tetex-upgrade.txt before
upgrading.
dropped and the lang/ruby16_r and lang/ruby18_r ports have been
removed, since no one seems to appreciate the partially working
solution.
Good news is that the pthread support of lang/ruby18 is now enabled by
default for newer systems, which means the ruby interpreter is linked
with libpthread. This will allow threaded extension libraries to run
and work properly on those systems.
The --march=cputype flag is disabled because it gets ruby to
malfunction and fail to build. I don't know if the problem is in
libpthread or in gcc.
(It really makes me wonder if they had actually tested before asking
me to do this somewhat risky change ;-)
