| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We rely on the tools framework to pull in a good enough awk tool.
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
variables into CONFIGURE_ENV if the new tools framework already takes
care of adding them automatically.
|
|
create the config file at do-configure time.
|
|
|
|
|
|
Changes since last packaged version (0.9.5)
* Version 0.9.6c, 2005-04-26
No changes list found, diff seems to show bug fixes and syslog improvements
* Version 0.9.6, 2005-04-03
* Summary:
The main goals for this version was to close all the outstanding bugs and
apply all the submitted patchs
on sourceforge. All the sourceforge easy to do RFE's where also included.
* Notes:
- Added support for mulpiple Base DN's
- Added support to log for syslog (Benjamin Drieu)
- Added hooks feature to replace custom functions (Benjamin Drieu)
- Entry chooser now auto adds rdn entry for copy/move operations (wigi2)
- Initial support for AD Schema Retrieval
- Added login restriction (Samuel Tran)
- Added support to move objects (aka Copy then Delete) (wigi2)
- No longer show + next to objects that have no children in tree viewer
(when hide_configuration_management=true)
- Added date evaluation to shadow attributes (shadowAccount)
- Added Enhancement to show attributes in a specifc order (Samuel Tran)
- Added Server Info OID descriptions
- Added new feature to compare two DNs
- Binary SID to text SID feature for MSAD objectSid entries.
- Added session timeout feature (Samuel Tran)
* New Languages:
- Taiwan (Anonymous)
- Simplfied Chinese (Anonymous)
* Changes:
- LDAP server configuration is being moved into an Object LDAPServer, all
future interactions should use this object class from now on.
- Some more conversions of english static text into language files.
- Some code cleanup, excess whitespace removal, etc...
- Tags for phpdoc updated.
- Added cvs header to files missing the header.
- LDIF Import function improvements (Xavier Renard)
- UniqueAttrs fix, now showing actual value (in multi value attribs) that
breaches uniqueness
- Fixed check_lang_files when register_globals=off
- css fixes (Daniel van Eeden)
- More locatisation fixes (Piotr Tarnowski)
- Schema functions all use cached entries now by default
- Improved password encoding functions (Tomas Kuliavas)
- If auth_type = session, then dn and password is also blowfish encrypted
- Prettied up the icon index (Dave Smith)
- Make the rdn not editable in the default template.
* Fixes:
- password_check when magic_quotes_gpc is on.
- Misc fixes (Benjamin Drieu)
- Fix searchs when searching for values with brackets
- Unicode fixes (Daniel van Eeden)
- View jpeg photo minor security fix (Dave Smith)
- Check password link missing in read-only mode
* Sourceforge bug fixes:
1117099 1117316 1120048 1150947 1152962 1153360 1055401 1158148 1161425
|
|
it with an explicit lang/perl58 reference.
|
|
Ok'd by jmmv@ and rh@ (gnome 1 maintainers).
|
|
|
|
DB is a database abstraction layer providing:
* an OO-style query API
* portability features that make programs written for one DBMS work with i
other DBMS's
* a DSN (data source name) format for specifying database servers
* prepare/execute (bind) emulation for databases that don't support it natively
* a result object for each query response
* portable error codes
* sequence emulation
* sequential and non-sequential row fetching as well as bulk fetching
* formats fetched rows as associative arrays, ordered arrays or objects
* row limit support
* transactions support
* table information interface
* DocBook and phpDocumentor API documentation
|
|
portable shell constructs.
|
|
which can take multiple values -- "pax" or "gtar". The default value
of EXTRACT_USING is "pax", which more closely matches reality since
before, we were using bootstrap "tar" for ${GTAR} and it was actually
pax-as-tar. Also, stop pretending pax-as-tar from the bootstrap kit
or on NetBSD is GNU tar. Lastly, in bsd.pkg.extract.mk, note whether
we need "pax" or "gtar" depending on what we need to extract the
distfiles.
|
|
|
|
|
|
restart picks it up, too.
|
|
Package change: convert to the options framework.
Changes since last packaged version (0.30):
perl-ldap 0.3202 -- Mon Jul 19 11:44:08 BST 2004
Bug Fixes
* Fixed case typo in Makefile.PL
perl-ldap 0.3201 -- Wed Jul 14 21:52:59 BST 2004
Bug Fixes
* Fixed dependancies in Makefile.PL
perl-ldap 0.32 --
Bug Fixes
* Documentation updates
* Fixed LDIF output from ldapsearch command
* Return an error if no filter is passed to Net::LDAP::filter->parse
* Fixed bug handling comments in LDIF parser
* Fix to ldapsearch for passing scope with -s
* Do not send a fake userid in SASL binds
* Net::LDAP::Schema->parse() now returns undef on errors
Enhancements
* Added supportedFeatures to the default list of attributes
fetched by ->root_dse
* Added option to sort attributes in LDIF output, with objectclass
being first floowed by all other attributes in alphabetical order
* Add escape/unescape filters/DN utility functions
* Added support for reading LDIF URL attributes using file://
* The socket created by new can now be bound to a local address & port
* Any controls returned by the server with each entry as a result from a
search are now available in the callback function
* Added classes for EntryChange, PersistentSearch and ManageDsaIT controls
* Allow options passed to Net::LDAP::Entry-.update to be passed to the
Net::LDAP method that is finally called
perl-ldap 0.31 1 Jan 2004
==========================
* Fixed bug that could cause methods to return an integer instead of an object
* Fixed bug causing Schema.pm to ignore superior classes that had no attributes
* Documentation updates
* Updates to LDIF module
|
|
This release contains a variety of fixes from 8.0.2, including several
security-related issues.
__________________________________________________________________
Migration to version 8.0.3
A dump/restore is not required for those running 8.0.X. However, it is
one possible way of handling two significant security problems that
have been found in the initial contents of 8.0.X system catalogs. A
dump/initdb/reload sequence using 8.0.3's initdb will automatically
correct these problems.
The larger security problem is that the built-in character set encoding
conversion functions can be invoked from SQL commands by unprivileged
users, but the functions were not designed for such use and are not
secure against malicious choices of arguments. The fix involves
changing the declared parameter list of these functions so that they
can no longer be invoked from SQL commands. (This does not affect their
normal use by the encoding conversion machinery.)
The lesser problem is that the "contrib/tsearch2" module creates
several functions that are misdeclared to return internal when they do
not accept internal arguments. This breaks type safety for all
functions using internal arguments.
It is strongly recommended that all installations repair these errors,
either by initdb or by following the manual repair procedure given
below. The errors at least allow unprivileged database users to crash
their server process, and may allow unprivileged users to gain the
privileges of a database superuser.
If you wish not to do an initdb, perform the same manual repair
procedures shown in the 7.4.8 release notes.
__________________________________________________________________
Changes
* Change encoding function signature to prevent misuse
* Change "contrib/tsearch2" to avoid unsafe use of INTERNAL function
results
* Guard against incorrect second parameter to record_out
* Repair ancient race condition that allowed a transaction to be seen
as committed for some purposes (eg SELECT FOR UPDATE) slightly
sooner than for other purposes
This is an extremely serious bug since it could lead to apparent
data inconsistencies being briefly visible to applications.
* Repair race condition between relation extension and VACUUM
This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low
probability. There are no known cases of it having caused more than
an Assert failure.
* Fix comparisons of TIME WITH TIME ZONE values
The comparison code was wrong in the case where the
--enable-integer-datetimes configuration switch had been used.
NOTE: if you have an index on a TIME WITH TIME ZONE column, it will
need to be "REINDEX"ed after installing this update, because the
fix corrects the sort order of column values.
* Fix EXTRACT(EPOCH) for TIME WITH TIME ZONE values
* Fix mis-display of negative fractional seconds in INTERVAL values
This error only occurred when the --enable-integer-datetimes
configuration switch had been used.
* Fix pg_dump to dump trigger names containing % correctly (Neil)
* Still more 64-bit fixes for "contrib/intagg"
* Prevent incorrect optimization of functions returning RECORD
* Prevent crash on COALESCE(NULL,NULL)
* Fix Borland makefile for libpq
* Fix "contrib/btree_gist" for timetz type (Teodor)
* Make "pg_ctl" check the PID found in "postmaster.pid" to see if it
is still a live process
* Fix "pg_dump"/"pg_restore" problems caused by addition of dump
timestamps
* Fix interaction between materializing holdable cursors and firing
deferred triggers during transaction commit
* Fix memory leak in SQL functions returning pass-by-reference data
types
pkgsrc specific change:
Instead of setting CONFIGURE_ART let configure find the template to use
iteself.
|
|
"MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level
make process, not the software's own make process.
|
|
to pass make flags to bmake.
|
|
The Announcement:
Berkeley DB 4.3.28 is a patch release to 4.3.27, everyone is encouraged
to update to this version. The following have been addressed in this
patch release:
1. All patches for the prior version have been applied as well
as a few other fixes.
2. The product is available as a Windows x86 binary installer
To see the change log for version 4.3.28, please visit:
http://www.sleepycat.com/updat e/4.3.27/if.4.3.27.html
|
|
options framework. Rename PKG_OPTIONS.* to PKG_BUILD_OPTIONS.*.
|
|
caches variable definitions that were computed by make. These variables
are specified by listing them in MAKE_VARS, e.g.,
.if !defined(FOO)
FOO!= very_time_consuming_command
.endif
MAKE_VARS+= FOO
bsd.pkg.mk will include only the one generated during the most recent
phase. A particular phase's makevars.mk file consists of variable
definitions that are a superset of all of the ones produced in previous
phases of the build.
The caching is useful because bsd.pkg.mk invokes make recursively,
which in the example above has the potential to run the very time-consuming
command each time unless we cause FOO to be defined for the sub-make
processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't
consistently applied to every invocation of make, and also because
MAKE_FLAGS can overflow the maximum length of a make variable very
quickly if we add many values to it.
One important and desirable property of variables cached via MAKE_VARS
is that they only apply to the current package, and not to any
dependencies whose builds may have been triggered by the current
package.
The makevars.mk files are generated by new targets fetch-vars,
extract-vars, patch-vars, etc., and these targets are built during
the corresponding real-* target to ensure that they are being invoked
with PKG_PHASE set to the proper value.
Also, remove the variables cache file that bsd.wrapper.mk was generating
since the new makevars.mk files provide the same functionality at a
higher level. Change all WRAPPER_VARS definitions that were used by
the old wrapper-phase cache file into MAKE_VARS definitions.
|
|
package because PKG_OPTION.<pkg> could contain negative options, which
are never part of PKG_OPTIONS. Instead, use the show-var target to
display the value. We cache it in WRAPPER_VARS and in MAKE_FLAGS to
prevent reinvoking the show-var target recursively.
|
|
|
|
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
|
|
Bump PKGREVISION of postgresql73-lib as plpgsql.so has changed (now
loads successfully).
|
|
|
|
|
|
shared object for Tcl clients.
This is based on, and almost identical to, the tcl-postgresql73 package,
but for PostgreSQL 7.4 rather than 7.3.
|
|
changes: minor bugfixes, translation updates
|
|
|
|
packages, and the original authors have stopped its maintenance.
Thus, there are various vulnerabilities in them now.
|
|
|
|
changes: bugfixes
|
|
on NetBSD 1.6.
|
|
- Support 64 bit integers (uses floating point numbers when perl is not
compiled with 64 bit int support). This also fixes issues with using
sqlite timestamps.
- Upgrade to sqlite 3.1.3
- Fix issues of not finding rows when providing a number that perl sees
as a string.
- Fixes for most current bugs in RT (see http://rt.cpan.org/ to check
if your favourite bug got fixed).
|
|
|
|
2005 March 29 (3.2.1)
* Fix a memory allocation error in the new ADD COLUMN comment.
* Documentation updates
2005 March 21 (3.2.0)
* Added support for ALTER TABLE ADD COLUMN.
* Added support for the "T" separator in ISO-8601 date/time strings.
* Improved support for Cygwin.
* Numerous bug fixes and documentation updates.
2005 March 16 (3.1.6)
* Fix a bug that could cause database corruption when inserting
record into tables with around 125 columns.
* sqlite3_step() is now much more likely to invoke the busy
handler and less likely to return SQLITE_BUSY.
* Fix memory leaks that used to occur after a malloc() failure.
2005 March 11 (3.1.5)
* The ioctl on OS-X to control syncing to disk is F_FULLFSYNC,
not F_FULLSYNC. The previous release had it wrong.
2005 March 10 (3.1.4)
* Fix a bug in autovacuum that could cause database corruption
if a CREATE UNIQUE INDEX fails because of a constraint violation.
This problem only occurs if the new autovacuum feature introduced
in version 3.1 is turned on.
* The F_FULLSYNC ioctl (currently only supported on OS-X) is
disabled if the synchronous pragma is set to something other
than "full".
* Add additional forward compatibility to the future version 3.2
database file format.
* Fix a bug in WHERE clauses of the form (rowid<'2')
* New SQLITE_OMIT_... compile-time options added
* Updates to the man page
* Remove the use of strcasecmp() from the shell
* Windows DLL exports symbols Tclsqlite_Init and Sqlite_Init
|
|
|
|
with share/postgresql80/timezone/Australia/Darwin
to fix non MacOS X machines. overenthusiastic search & replace?
|
|
- Add a few sites to MASTER_SITES.
|
|
|
|
|
|
(Forgot to remove this in the previous commit.)
|
|
While at it do some structual changes to packages and merge
the lib and docs package has been merged into the client package.
Also enable Rendezvous support on Darwin.
Changes
* Increment the major version number of all interface libraries
(Bruce)
This should have been done in 8.0.0. It is required so 7.4.X
versions of PostgreSQL client applications, like psql, can be used
on the same machine as 8.0.X applications. This might require
re-linking user applications that use these libraries.
* Add Windows-only wal_sync_method setting of "fsync_writethrough"
(Magnus, Bruce)
This setting causes PostgreSQL to write through any disk-drive
write cache when writing to WAL. This behavior was formerly called
"fsync", but was renamed because it acts quite differently from
"fsync" on other platforms.
* Enable the wal_sync_method setting of "open_datasync" on Windows,
and make it the default for that platform (Magnus, Bruce)
Because the default is no longer "fsync_writethrough", data loss is
possible during a power failure if the disk drive has write caching
enabled. To turn off the write cache on Windows, from the Device
Manager, choose the drive properties, then Policies.
* New cache management algorithm 2Q replaces ARC (Tom)
This was done to avoid a pending US patent on ARC. The 2Q code
might be a few percentage points slower than ARC for some work
loads. A better cache management algorithm will appear in 8.1.
* Planner adjustments to improve behavior on freshly-created tables
(Tom)
* Allow plpgsql to assign to an element of an array that is initially
NULL (Tom)
Formerly the array would remain NULL, but now it becomes a
single-element array. The main SQL engine was changed to handle
"UPDATE" of a null array value this way in 8.0, but the similar
case in plpgsql was overlooked.
* Convert \r\n and \r to \n in plpython function bodies (Michael
Fuhr)
This prevents syntax errors when plpython code is written on a
Windows or Mac client.
* Allow SPI cursors to handle utility commands that return rows, such
as "EXPLAIN" (Tom)
* Fix "CLUSTER" failure after "ALTER TABLE SET WITHOUT OIDS" (Tom)
* Reduce memory usage of "ALTER TABLE ADD COLUMN" (Neil)
* Fix "ALTER LANGUAGE RENAME" (Tom)
* Document the Windows-only register and unregister options of pg_ctl
(Magnus)
* Ensure operations done during backend shutdown are counted by
statistics collector
This is expected to resolve reports of pg_autovacuum not vacuuming
the system catalogs often enough -- it was not being told about
catalog deletions caused by temporary table removal during backend
exit.
* Change the Windows default for configuration parameter
log_destination to "eventlog" (Magnus)
By default, a server running on Windows will now send log output to
the Windows event logger rather than standard error.
* Make Kerberos authentication work on Windows (Magnus)
* Allow "ALTER DATABASE RENAME" by superusers who aren't flagged as
having CREATEDB privilege (Tom)
* Modify WAL log entries for "CREATE" and "DROP DATABASE" to not
specify absolute paths (Tom)
This allows point-in-time recovery on a different machine with
possibly different database location. Note that "CREATE TABLESPACE"
still poses a hazard in such situations.
* Fix crash from a backend exiting with an open transaction that
created a table and opened a cursor on it (Tom)
* Fix array_map() so it can call PL functions (Tom)
* Several "contrib/tsearch2" and "contrib/btree_gist" fixes (Teodor)
* Fix crash of some "contrib/pgcrypto" functions on some platforms
(Marko Kreen)
* Fix "contrib/intagg" for 64-bit platforms (Tom)
* Fix ecpg bugs in parsing of "CREATE" statement (Michael)
* Work around gcc bug on powerpc and amd64 causing problems in ecpg
(Christof Petig)
* Do not use locale-aware versions of upper(), lower(), and initcap()
when the locale is C (Bruce)
This allows these functions to work on platforms that generate
errors for non-7-bit data when the locale is C.
* Fix quote_ident() to quote names that match keywords (Tom)
* Fix to_date() to behave reasonably when CC and YY fields are both
used (Karel)
* Prevent to_char(interval) from failing when given a zero-month
interval (Tom)
* Fix wrong week returned by date_trunc('week') (Bruce)
date_trunc('week') returned the wrong year for the first few days
of January in some years.
* Use the correct default mask length for class D addresses in INET
data types (Tom)
|
|
|
|
Active Record connects business objects and database tables to create
a persistable domain model where logic and data is presented in one
wrapping. It is an implementation of the object-relational mapping
(ORM) pattern by the same name as described by Martin Fowler:
"An object that wraps a row in a database table or view, encapsulates
the database access, and adds domain logic on that data."
Active Records main contribution to the pattern is to relieve the
original of two stunting problems: lack of associations and
inheritance. By adding a simple domain language-like set of macros to
describe the former and integrating the Single Table Inheritance
pattern for the latter, Active Record narrows the gap of functionality
between the data mapper and active record approach.
|
|
|
|
|
