- repoint x11-toolkits/gtk-sharp10 dependencies to www/gecko-sharp10 so
the Gecko renderer is always built.
- Correct pkg-plist for gacutil changes with Mono 1.1.9.x
- Include bsd.mono.mk.
Approved by: ahze (mentor)
Project by: BSD# <http://www.mono-project.com/Mono:FreeBSD>
- Remove PKGNAMESUFFIX, we don't need this.
- Remove libgnomedb# and gda#, libgnomedb and gda are no lobnger part
of Gnome.
- Add support for gtkhtml 3.8
- Correct pkg-plist for gacutil changes with Mono 1.1.9.x
- Include bsd.mono.mk.
Submitted by: Soeren Straarup <xride@x12.dk>
Approved by: ahze (mentor)
Project by: BSD# <http://www.mono-project.com/Mono:FreeBSD>
of Gnome.
- Add support for gtkhtml 3.8
- Correct pkg-plist for gacutil changes with Mono 1.1.9.x
- Include bsd.mono.mk.
Approved by: ahze (mentor)
Project by: BSD# <http://www.mono-project.com/Mono:FreeBSD>
Mono Changes:
- Series release: http://www.go-mono.com/archive/1.1.9/
- Patch release: http://www.go-mono.com/archive/1.1.9.1_0/
(No 1.1.9.2 release announcement.)
Port Changes:
- Add pkg-message to explain reasons for common build failures and
note the need to possibly increase the number of semaphores from
the default FreeBSD amounts.
- Add preliminary amd64 support [1,2] which has been disabled for
the time being due to lingering stability issues.
- Force the Mono build to only write within ${WRKDIR} and no longer
write to ~/.wapi which leads to...
- Add bsd.mono.mk which is a common makefile all Mono consumers will
depend on. Currently this file sets the location of the .wapi the
build process will write to. Since Mono does not cleanup the
semaphore created for a .wapi when the last Mono process exits
this file also handles the removal of the semaphore created during
port building so we do not exhaust the machine's semaphore limit.
Submitted by: Jean-Michel "tuo" Herve <jm.herve@gameproduction.org> [1]
Joe Lewis <joe@joe-lewis.com> [1]
Lou Kamenov on BSD# mailinglist [2]
Approved by: ahze (mentor)
Project by: BSD# <http://www.mono-project.com/Mono:FreeBSD>
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
* At user's request portmanager now respects a defined BATCH
* -sl works again, -sl and -slid options no longer consider
build dependencies as "leaves"
PR: 88744
Submitted by: Michael C. Shultz <ringworm01@gmail.com> (maintainer)
from Canonical. The difference between this and bazaar-ng is that this is the
"mainline" version of bazaar, beeing faster and more stable, while bazaar-ng is
the somwhat future platform. I thought it would be nice to have this in ports
as well, this is a very good implemenation that is easy to use, much easier
than TLA.
PR: ports/88476
Submitted by: Ulf Lilleengen <lulf@kerneled.org>
On recent FreeBSD installing multimedia/mplayer port doesn't
compile-in bsdbt848 driver. Cause for this is in the mplayer's
'configure' script that uses the following code to autodetect
the presense of the system bt848 driver:
if defined(__NetBSD__)
#include <dev/ic/bt8xx.h>
#else
#include <machine/ioctl_bt848.h>
#endif
On FreeBSD /usr/include/machine/ioctl_bt848.h is replaced
with /usr/include/dev/bktr/ioctl_bt848.h, so 'configure'
script doesn't find it. Be warned that if you upgraded
your FreeBSD installation from the older version, you will
still have /usr/include/machine/ioctl_bt848.h installed on
your system (make installworld doesn't delete old files)
and configure script will not need patching to be able to
find the system bt848 driver. In the fix section I attached
a patched 'files/patch-ad' file.
[...]
Hi again,
I've prepared a diff to solve the issue. Besides this,
PORTREVISION is bumped to reflect the change and distinfo
contains sha256 sum. Would you please confirm that it works
on amd64, go for the commit and close the pr?!
Submitted by: Simun Mikecin <numisemis@yahoo.com>
Approved by: "Thomas E. Zander" <riggs@rrr.de>
Reviewed by: Simun Mikecin <numisemis@yahoo.com>
PR: ports/87853
- Drop 4.x support because new version requires wscanf(), vswprintf() and so on
and tarballs of older versions are no longer available
- Fix build when howl installed [1]
- Remove USE_LIBLTDL which is no-op for this port [2]
- Do not build with postgresql, odbc, mysql or sqlite support
Reported by: vs [1], [2]
up-to-the-second blackhole list server designed to monitor global network
activity and make decisions based on network spread and infection rate -
that is, abuse from an address which has been reported by a number of
participating networks. This is in far contrast to how most other
blacklists function, where fallable humans (many with political agendas) must
process thousands of reports and make decisions - many times after the fact.
The RABL is fully reactive to new threats and can block addresses within
seconds of widespread infection - good to know in this world of drone PCs
and stolen accounts. The RABL server blacklists addresses until they have
cleared a minimum duration (an hour by default) without any additional
reporting, making the appeals process as simple as "fix your junk". The RABL
is designed to function via automated machine-learning spam filters, such as
Bayesian filters. Each participating network is granted write authentication
in the blackhole list, to prevent abuse. A client tool is also provided.
PR: ports/88446
Submitted by: Ion-Mihai "IOnut" Tetcu <itetcu@people.tecnik93.com>
