EXISTS counts after acknowledging EXPUNGE see <http://bugs.debian.org/314509>
- add fetchmailconf wrapper check for _tkinter.so (if python was installed but
not Tkinter, the wrapper would still try to run fetchmailconf.bin, which
gives a less clear error message to the user than was intended)
- let fetchmailconf wrapper pass command line arguments to fetchmailconf.bin
(it supports -d and -f FILE)
- replace PREFIX with LOCALBASE where appropriate
- bump PORTREVISION
Submitted by: Matthias Andree <matthias.andree@gmx.de>
PR: ports/88444
- Correct numerous DllImport errors. The C symbol must be defined in the
C library that is being imported. Not sure why this is not a problem
on Linux.
- Include bsd.mono.mk.
Approved by: ahze (mentor)
Project by: BSD# <http://www.mono-project.com/Mono:FreeBSD>
- 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
