Changes:
* Umbrello
o Export all views
o Static variables in java code are not marked static
o New alignment type "distribute horizontally/vertically"
o Save autosave file to a more obvious place
o Usability and responsiveness improvements to code import
o Auto-complete in parameter properties dialog in class diagram
o Don't crash on application exit
o Memory problem when importing classes from C++ sources
o Nestable components and subsystems in Component diagram
o Switch back to arrow tool after association creation
o Fix crash loading xmi file
o User interaction with UMLWidget improvements
o Comments are cut short when generating PHP code
o Freeze on C++ class import
o Fix crash on importing Java 1.5 classes containing annotations
* KCacheGrind
o "Fix slow handling (loading, cycle detection, drawing the call
graph) of profiles where functions have number of callers/callees
in the thousands. These unusual profiles are typically produced
by running callgrind on Valgrind itself (so called Valgrind
self-hosting)."
by always forcing our internal search path when invocing bmake.boot.
This does not affect the generated binary and is the reason why this
goes directly into the tree.
02-may-2006 Version 0.9.22: lots of major changes, monotone 0.26,
bazaar-ng 0.8, dropped mercurial CLI backend replaced by former
hglib, dropped obsolete and incomplete svndump.
28-may-2006 Version 0.9.23: again several major changes, most
notably preserve the hunks order, and workaround to darcs changes
--xml out of order output.
Major changes between Mercurial 0.8.1 and 0.9:
- The repository file format has been improved.
- This has resulted in an average 40% reduction in disk space usage.
- The new format (called RevlogNG) is now the default.
- Mercurial works perfectly with both the old and new repository
file formats. It can transfer changes transparently between
repositories of either format.
- To use the new repository format, simply use `hg clone --pull` to
clone an existing repository.
- Note: Versions 0.8.1 and earlier of Mercurial cannot read
RevlogNG repositories directly, but they can `clone`, `pull`
from, and `push` to servers that are serving RevlogNG
repositories.
- Memory usage has been improved by over 50% for many common operations.
- Substantial performance improvements on large repositories.
- New commands:
- 'archive' - generate a directory tree snapshot, tarball, or zip
file of a revision
- Deprecated commands:
- 'addremove' - replaced by 'add' and 'remove --after'
- 'forget' - replaced by 'revert'
- 'undo' - replaced by 'rollback'
- New extensions:
- Bugzilla integration hook
- Email notification hook
- Nested repositories are now supported. Mercurial will not recurse
into a subdirectory that contains a '.hg' directory. It is treated
as a separate repository.
- The standalone web server, 'hg serve', is now threaded, so it can
talk to multiple clients at a time.
- The web server can now display a "message of the day".
- Support added for hooks written in Python.
- Many improvements and clarifications to built-in help.
Sort PLIST.
* The distribution terms for all Bison-generated parsers now permit
using the parsers in nonfree programs. Previously, this permission
was granted only for Bison-generated LALR(1) parsers in C.
* %name-prefix changes the namespace name in C++ outputs.
* The C++ parsers export their token_type.
* Bison now allows multiple %union declarations, and concatenates
their contents together.
* New warning: unused values
Right-hand side symbols whose values are not used are reported,
if the symbols have destructors. For instance:
exp: exp "?" exp ":" exp { $1 ? $1 : $3; }
| exp "+" exp
;
will trigger a warning about $$ and $5 in the first rule, and $3 in
the second ($1 is copied to $$ by the default rule). This example
most likely contains three errors, and could be rewritten as:
exp: exp "?" exp ":" exp
{ $$ = $1 ? $3 : $5; free ($1 ? $5 : $3); free ($1); }
| exp "+" exp
{ $$ = $1 ? $1 : $3; if ($1) free ($3); }
;
However, if the original actions were really intended, memory leaks
and all, the warnings can be suppressed by letting Bison believe the
values are used, e.g.:
exp: exp "?" exp ":" exp { $1 ? $1 : $3; (void) ($$, $5); }
| exp "+" exp { $$ = $1; (void) $3; }
;
If there are mid-rule actions, the warning is issued if no action
uses it. The following triggers no warning: $1 and $3 are used.
exp: exp { push ($1); } '+' exp { push ($3); sum (); };
The warning is intended to help catching lost values and memory leaks.
If a value is ignored, its associated memory typically is not reclaimed.
* %destructor vs. YYABORT, YYACCEPT, and YYERROR.
Destructors are now called when user code invokes YYABORT, YYACCEPT,
and YYERROR, for all objects on the stack, other than objects
corresponding to the right-hand side of the current rule.
* %expect, %expect-rr
Incorrect numbers of expected conflicts are now actual errors,
instead of warnings.
* GLR, YACC parsers.
The %parse-params are available in the destructors (and the
experimental printers) as per the documentation.
* Bison now warns if it finds a stray `$' or `@' in an action.
* %require "VERSION"
This specifies that the grammar file depends on features implemented
in Bison version VERSION or higher.
* lalr1.cc: The token and value types are now class members.
The tokens were defined as free form enums and cpp macros. YYSTYPE
was defined as a free form union. They are now class members:
tokens are enumerations of the `yy::parser::token' struct, and the
semantic values have the `yy::parser::semantic_type' type.
If you do not want or can update to this scheme, the directive
`%define "global_tokens_and_yystype" "1"' triggers the global
definition of tokens and YYSTYPE. This change is suitable both
for previous releases of Bison, and this one.
If you wish to update, then make sure older version of Bison will
fail using `%require "2.2"'.
* DJGPP support added.
changes from 1.0.10 to 1.0.11
-----------------------------
* cvsd-buildroot should now install libraries in the same directory structure
as on the normal filesystem, resulting in better support for 64 bit systems
* other small improvements to cvsd-buildroot, including better error handling
and not overwriting devices
* small code improvements
> - 7037: [security] Port: Login with disabled account possible (vboctor)
> - 7034: [bugtracker] Port: bug in string_sanitize_url() (vboctor)
> - 7028: [db mssql] Port: "Prune Accounts" function doesn't work with MS SQL (vboctor)
> - 7029: [db mssql] Port: MS SQL Error on View Filters Page (vboctor)
> - 7030: [db mssql] Port: installtion fails - administrator have no rights on db (vboctor)
> - 7032: [db mssql] Port: Error on opening Change Log (vboctor)
> - 7039: [db mssql] Notice: Only variables should be assigned by reference in coreadodbadodb.inc.php on line 2931 (vboctor)
> - 7035: [feature] Port: Global Profiles list not sorted (vboctor)
> - 7038: [filters] Port: SYSTEM WARNING: Argument 1 to array_multisort() is expected to be an array or a sort flag (vboctor)
> - 7031: [installation] Port: is_writable never success in install.php (vboctor)
> - 7041: [installation] Port: newbie admins may be redirected to blank page (vboctor)
> - 7033: [printing] Port: wrong strpos function call (vboctor)
> - 7027: [upgrade] Port: fixed_in_version is renamed to Fixed_in_version during database migration (vboctor)
Changes since previous version:
+ include "compat.h" for a definition of the uuid_t structure - fixes
the build on Solaris (thanks to John Weekley for testing the fix).
This should also fix a problem in the bulk build.
+ rewrite the report_luns() function to something which is much easier
to read, and following Dan Carosone's and Matt Green's suggestions.
+ abstract the htobe64() function if it is available
+ tested only with little-endian initiators so far
+ bump version to 20060526
it will live with other "check" targets run after package installation.
Get rid of SHLIB_HANDLING, whose meaning had mutated over the years
from one thing to another. Currently, it is used to basically note
whether the system's "ldd" command can be usefully run on the package's
binaries and libraries. Rename this variable to CHECK_SHLIBS_SUPPORTED
for more clarity.
CHECK_SHLIBS is now a variable set exclusively by the user in /etc/mk.conf
to note whether the check for missing run-time search paths is performed
after a package is installed. It defaults to "no" unless PKG_DEVELOPER
is set.
* gmmproc: Corrections to code generation, to prevent some methods from being empty.
This was a regression introduced by the addition of the --enable-api-* options.
Adjust the data VPD returns, to work around a problem in the Cisco
initiator (used on Solaris 10 Update 1) - the initiator demands that a
UUID is returned, so give it one.
Add autoconf glue for that, and a compat uuid_create(3) and
uuid_to_string(3).
This still spews a lot of output via the target's syslog, but persevere,
since it does actually make the target work with the Solaris initiator:
solaris10# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1d0 <DEFAULT cyl 29728 alt 2 hd 64 sec 63>
/pci@0,0/pci-ide@1f,1/ide@0/cmdk@0,0
1. c2t5d0 <DEFAULT cyl 96 alt 2 hd 64 sec 32>
/iscsi/disk@0000iqn.1994-04.org.netbsd.iscsi-target%3Atarget00001,0
Specify disk (enter its number): ^D
solaris10# df -k /mnt
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c2t5d0s0 91407 1041 81226 2% /mnt
solaris10# uname -a
SunOS solaris10 5.10 Generic_118844-26 i86pc i386 i86pc
solaris10#
