Update DEPENDS
Upstream changes:
1.004002 - 2013-12-31
- fix type inflation in threads when types are inserted by manually
stringifying the type first (like Type::Tiny)
- add undefer_all to Sub::Defer
1.004001 - 2013-12-27
- fix repository links in pod
- add missing changelog entry regarding strictures to 1.004000 release
1.004000 - 2013-12-26
- strictures will now be applied to modules using Moo just as if they
included "use strictures" directly. This means that strictures extra
checks will now apply to code in checkouts.
- fix handling of type inflation when used with threads
- don't include meta method when consuming Mouse roles
- inhale Moose roles for has attr => ( handles => "RoleName" )
- provide useful error if attribute defined as required but with
init_arg => undef
- document that BUILDARGS isn't called when there are no attributes
- omit sub imported before use Moo from Moose method inflation
- check for FOREIGNBUILDARGS only once per class instead of on each
instantiation
- take advantage of XS predicates from newer versions of Class::XSAccessor
- always try to load superclasses and roles, and only fall back on the
heuristic of checking for subs if the file doesn't exist
- fix handling of attributes with names that aren't valid identifiers
- Quoted subs now preserve the package and pragmas from their calling code
- the official Moo git repository has moved to the Moose organization on
GitHub: https://github.com/moose/Moo
* "git diff -- ':(icase)makefile'" was unnecessarily rejected at the
command line parser.
* "git cat-file --batch-check=ok" did not check the existence of
the named object.
* "git am --abort" sometimes complained about not being able to write
a tree with an 0{40} object in it.
* Two processes creating loose objects at the same time could have
failed unnecessarily when the name of their new objects started
with the same byte value, due to a race condition.
Also contains typofixes, documentation updates and trivial code clean-ups
Update DEPENDS
Upstream changes:
0.12 Fri, 01 Nov 2013
* Fix detection when loaded during global destruction by checking B::main_cv
instead of B::main_start
* Bump Sub::Exporter::Progressive dependency to fix loading in global
destruction
0.11 Wed, 03 Apr 2013
* Fix upgrading from version 0.09 or older
0.10 Tue, 26 Mar 2013
* Rewrite pure-perl implementation in terms of B::main_start
(greatly simplifies code)
* Fix pure-perl behavior under $^C (RT#78619))
* Separate XS portion into a compiler-optional dependency
Devel::GlobalDestruction::XS
Remove the patch which included into src upstream
Upstream changes:
1.002000 - 2013-12-10
- allow specifying by caller level, as well as specifying file, line,
and version
1.001001 2013-03-25
- fix NAME in Makefile.PL (RT#84207)
Newt is a windowing toolkit for text mode built from the slang
library. It allows color text mode applications to easily use
stackable windows, push buttons, check boxes, radio buttons, lists,
entry fields, labels, and displayable text. Scrollbars are supported,
and forms may be nested to provide extra functionality.
Besides the newt library, this package provides whiptail, which may
be used from shell scripts similarly to Savio Lam's "dialog". Newt
provides the textual interface for the Red Hat and Debian boot
disks.
This package contains the python bindings for newt.
I do not know why older version is removed, this is required by
upcomming misc/byobu's configuration window.
Changelog:
Changes in version 2.7.1:
* Two critical bug fixes in the "diff --git" format support.
* Clarify the message printed when a patch is expected to empty out and delete
a file, but the file does not become empty.
* Various improvements to messages when applying a patch to a file of different
type (regular file vs. symlink), when there are line ending differences (LF
vs. CRLF), and when in --dry-run mode.
* When in the root directory, allow file names that are absolute or that
contain a component of "..".
* New --follow-symlinks option to allow to treat symlinks as files: this was
patch's behavior before version 2.7.
* Ignore when extended attributes cannot be preserved because they are
unsupported or because permission to set them is denied.
* License clarifications in NEWS and README.
* Portability bug fixes.
Changes in version 2.7:
* Patch no longer gets a failed assertion for certain mangled patches.
* Ignore destination file names that are absolute or that contain a component
of "..". This addresses CVE-2010-4651.
* Support for most features of the "diff --git" format, including renames and
copies, permission changes, and symlink diffs. Binary diffs are not
supported yet; patch will complain and skip them.
* Support for double-quoted filenames: when a filename starts with a double
quote, it is interpreted as a C string literal. The escape sequences \\, \",
\a, \b, \f, \n, \r, \t, \v, and \ooo (a three-digit octal number between 0
and 255) are recognized.
* Refuse to apply a normal patch to a symlink. (Previous versions of patch
were replacing the symlink with a regular file.)
* When trying to modify a read-only file, warn about the potential problem
by default. The --read-only command line option allows to change this
behavior.
* Files to be deleted are deleted once the entire input has been processed, not
immediately. This fixes a bug with numbered backup files.
* When a timestamp specifies a time zone, honor that instead of assuming the
local time zone (--set-date) or Universal Coordinated Time (--set-utc).
* Support for nanosecond precision timestamps.
* Many portability and bug fixes.
Changes in version 2.6.1:
* Support for diff3(1) style merges which show the old, original, and new lines
of a conflict has been added (--merge=diff3). The default still is the
merge(1) format (--merge or --merge=merge).
* Bug and portability fixes.
Changes in version 2.6:
* A regression test suite has been added ("make check").
* A --merge option has been added which will merge a patch file into
the original files similar to merge(1). See the patch(1) manual page for
documentation.
* Unless a filename has been specified on the command line, look only
for filenames in the patch until one has been found. This prevents
patch from tripping over garbage that isn't a patch. When conforming
to POSIX, this behavior is turned off and patch will ask for a
filename if none is found.
* All reject files have file name headers, which allows them to be used as
regular patches.
* When a patch file modifies the same file more than once, patch makes
sure it backs up the original version of the file rather than any
intermediary versions.
* In the above situation, if there are rejects in more than one of those
patches, they all go into the same reject file.
* When the file to be patched is specified on the command line, all patches
are applied to that file. (Previously, the first patch was applied to the
file specified on the command line, and the names of additional files to
patch were taken from header lines in the patch file.)
* The -r option now works correctly even if there are rejects in more than
one file. Use the - argument to discard rejects.
* Rejected hunks come out in unified diff format if the input patch was of
that format, otherwise in ordinary context diff form. Use the
--reject-format option to enforce either "context" or "unified" format.
Timestamps and the "diff -p" (--show-c-function) output are preserved.
Changed lines in context format reject files are correctly indicated
with '!' markers as the format defines. Added and removed lines are
still marked with '+' and '-', respectively.
* The file permissions of reject files are no longer set to match the files
they modify. Instead, they retain the default permissions. This is
consistent with reject files produced with the -r option.
* The --binary option disables the heuristic for stripping CRs from
line endings in patches. This allows to preserve CRs even in mangled
patches, or in patches generated on non-POSIX systems and without the
--binary option.
* Backup files for nonexisting files are now created with default
permissions rather than with mode 0: backup files with mode 0 were
causing problems with applications which do not expect unreadable
files.
* The -B, -Y, and -z options (--prefix, --basename-prefix, --suffix) now
imply the simple version control mode, and can be combined.
* Patch rejects more malformed normal format commands and checks for trailing
garbage. It now recognizes ed commands without addresses.
* Change the default value of PATCH_GET to 0. (Previously, the default was 0
under POSIXLY_CORRECT and negative otherwise; this is causing problems
particularly with Perforce.)
* Handle missing timestamps better.
* Various bug fixes.
* Switch to GNU General Public License version 3.
Changelog:
4.2.1:
This release is primarily a bugfix release; notable changes include:
Oracle:
* Resolve numerous issues with the 4.0 -> 4.2 upgrade steps on Oracle
* In-database sessions on Oracle are no longer truncated at 8k,
leading to spurious logouts
Internet Explorer:
* Fix submission issues under Internet Explorer
Rich text editor:
* If returning to a reply/correspond page with the back button, the
rich text editor will no longer double-escape previously written
content.
REST:
* Fix an empty 'text/plain' part when tickets are created using the
REST interface.
Other bugfixes:
* Optimize transaction display code to speed up long ticket displays
by short-circuiting transaction custom field checking.
* Supply a default $PATH for SMIME and GnuPG under FastCGI
* Support index upgrade steps on Pg when in a custom schema
* Close a memory leak in ColumnMap
* Fix "check all" checkboxes for new jQuery version
* Secondarily sort user ticket lists by id, as well as priority.
* Remove call to deprecated function used by PreviewScripMessages
* Many localization fixes (thanks to Emmanuel Lacour)
* Show customized rights in their correct tabs
* Ensure RFC2822 date format uses two-digit days in output
* Display iCal dates in the user's timezone, resolving off-by-one
errors for timezones significantly off from GMT.
* Correctly parse complex format strings for listing in the bottom of
the Query Builder
Callbacks:
* Move ModifyQueryProperties callback to before its values are used
* Additional callbacks on ticket modify pages
* Additional callbacks on ticket reply/comment page
* Additional callback on search results page
* Additional callback before transactions in history list
* Allow header callback to modify %ARGS
Features
* Allow bulk update to delete _all_ CF values for a given CF
* Support CF.Foo in columnmaps, in addition to CF.{Foo} and
__CF.{Foo}__
* Autocompletion CFs now autocomplete in search builder
* Support cascaded selects with any combination of listbox, dropdown,
and radio button
* Support ShowUnreadMessageNotifications in SelfService
4.2.0:
RT 4.2.0 -- 2013-10-03
----------------------
We're incredibly pleased to announce the availability of RT 4.2.0 - the
first release for the next major version of RT. This release adds
exciting new functionality, as well as streamlining and generalizing the
internals.
When upgrading, please be sure to review the upgrading documentation
available in docs/UPGRADING-4.2, as there are a number of
backward-incompatible changes that come along with the new version
number. Upgrading documentation is also available at
http://www.bestpractical.com/docs/rt/latest/UPGRADING-4.2.htmlhttp://download.bestpractical.com/pub/rt/release/rt-4.2.0.tar.gzhttp://download.bestpractical.com/pub/rt/release/rt-4.2.0.tar.gz.asc
a24bd767263cdcee92bf52c6b06a1a573aa0a615 rt-4.2.0.tar.gz
0717fd7d928efaadba2228de855c014e6be735cb rt-4.2.0.tar.gz.asc
A partial list of the new features in RT 4.2.0 is included below, and on
http://bestpractical.com/rt/whats-new/ Many of the new features will also
be described and demoed in a series of blog posts on
http://blog.bestpractical.com/ in the coming weeks.
If you have questions as you upgrade, please don't hesitate to write to
rt-users@lists.bestpractical.com for community support. If you'd rather
have professional support from the folks who built RT, drop us a line at
contact@bestpractical.com.
- Alex Vandiver, for Best Practical
* Much improved reporting via search result charting
- Multiple group by and statistic calculations in a table
- Time statistics such as average, minimum, and maximum durations
between Created and Resolved, Created and Started, Started and
Resolved, and more.
- More robust layout of charts
* Increased performance for searches and ticket pages
- Faster searches on all databases (especially Pg)
- Ticket pages load quicker
- Menus load before the rest of the page is loaded
- History is loaded asynchronously
- Faster serving of static assets
* Scrips per queue
- Apply scrips globally or ad-hoc to individual queues, a la custom
fields
- Less duplication of scrips and/or need for empty templates
* Custom field groupings
- Display CFs in configurable groupings (boxes) on the ticket
display/edit pages
- Includes arbitrary grouping names as well as standard ticket
groupings (Basics, Dates, People, Links, etc.)
* User summary pages
- Display information about users such as tickets, history, groups,
etc.
- An extended "More about requestors" page for any user
- Easy to get to via links and user search
* HTML templates enabled by default for new installs, available for
upgrades too
* History improvements
- Rich text/HTML messages are preferred for display by default
- Images are inlined with text in ticket history display instead of
presented at bottom
- Clickable users, tickets, articles, and other items
* Many interface improvements, such as:
- Per-user preferences for the dashboards which appear in the Home
menu
- Floating page menu for quicker access to ticket actions, subpages,
etc.
- Autocomplete for ticket links, including when merging
- Autocomplete available to self service users
- Improved CF and links display in search results
- Sticky simple search for quick search refinements
- Attachments on reply can no longer be mixed up when replying to
multiple tickets at once
- ReassignTicket right to assign tickets without stealing first;
useful for managers
* S/MIME support integrated with GnuPG support
- Decrypt and verify incoming GPG and SMIME messages
- Send all outgoing messages as either GPG or SMIME
* Migration tools
- Migrate from one database type to another (MySQL, Pg, Oracle)
- Merge multiple RT instances together
* Thousands of bug fixes; nearly 2000 commits totalling more than
250,000 lines of code changed.
4.0.18:
This release is primarily a bugfix release; most notably, it addresses
compatibility issues with recent versions of the Encode perl module.
Notable changes include:
Email
* Cope with Encode version 2.33 and later, which altered their internal
functionality and caused RT to double-encode Subject lines in
outgoing email.
* Fix HTML rendering errors in dashboard emails.
* Fix overzealous quoting around decoded MIME words.
Administration
* In the rights UI, entering the name of a user or group which already
has rights will now correctly select them for rights granting, as if
their name had been selected.
* Display types in the "applies to" dropdown for custom fields in
consistent order
* Paginate the Queues list in the administrative interface into 50
results per page.
* Support for cascading selections with a multiple-select parent.
* Clarify that $ParseNewMessageForTicketCcs only applies to new, and
not existing, tickets.
* Clarify how an undefined $RTAddressRegexp is treated, and that it
does not come at any notable performance penalty.
Logging
* Fix verbosity of syslog messages; now only the 'debug' level includes
originating filename and line.
* Include process ID in log messages, for ease of isolation in a
multi-process environment.
* Log the From: address of incoming mail which triggered an error, for
ease of debugging.
Other Bugfixes
* Avoid linking trailing punctuation, or html tags, in URL anchors in
MakeClicky
* Fix the Quick Search (QueueSummary) portlet when non-lowercase statuses are used.
* Show Date and DateTime custom fields in the user's format and time
zone in search results.
* Allow rt-email-group-admin to be passed an email address that RT is
not already aware of.
* Show submitted content from the user on errors in REST submission,
for ease of re-editing and re-submission.
* Convert to build from source to configure the localtion of configuration.xml.
Prebuild binary requires /var/opengrok directory. This package requires
the directory inside ${PREFIX}/share/opengrok only.
* Update HOMEPAGE
Changelog:
0.12-rc5:
differentiate between raw and download #578
add H A D links to directory listing #573
fix dtags.eftar file descriptor leak #535
do not unnecessarily create 2 File objects when returning eftar reader #539
0.12-rc4:
highlight line number with anchor (#702)
timeout for command execution (#429, #487)
fix for definitions search displays comment lines (#294)
0.12-rc3:
Lucene 4.6.0
Mercurial rename regression fix (#683)
let sendToConfigHost body use the parameter "env" to keep align with its signature and other methods
0.12-rc2:
bug #672 need double-quotes to specify path
bug #625 xref links containing \u don't seem to be working
follow-up fixes for Mercurial renamed files handling (fixes#666)
Support for Surround SCM history
lucene 4.5 (requires full reindex from 0.12-rc1)
generate history of files renamed in Mercurial repo separately (fixes#22)
0.12-rc1:
JDK7 + tomcat7 tested, JDK6 unsupported!
lucene 4.4 -> A LOT faster engine, no spellindex needed, regexp search supported (see help)
pl/sql, scala, uuencode languages/analyzers support
php analyzers improved
monotone, mercurial SCM support improved
AccuRev SCM added to supported SCMs
new config options in OpenGrok script
new search by analyzer/language
Changelog for <0.12 is not available.
Changelog:
JFlex 1.4.3 (Jan 31, 2009) fixes all known bugs of 1.4.2
Fixed bug #2018299 (lookahead syntax error).
Fixed bug #2010261 (min_int in Java example scanner).
Fixed bug #2007221 (zzEOFDone not reset in yyreset(Reader)).
Fixed bug #1999301 (%type and %int at the same time should produce error message).
JFlex 1.4.2 (May 27, 2008) fixes all known bugs of 1.4.1
Implemented feature request #1212181: Now supports generics syntax for %type, %extends, etc.
Implemented feature request #1762500: Provided %ctorarg option to add arguments to constructor.
Fixed bug #1464525 (Reader.read might return 0).
Fixed bug #1968897 (Ambiguous error message in macro expansion).
Fixed bug #1832973 (Syntax error in input may cause NullPointerException).
Fixed bug #1629920 (Need to defend against path blanks in jflex bash script).
Fixed bug #1540228 (EOF actions may be ignored for same lex state).
Fixed bug #1498726 (syntax error in generated ZZ_CMAP).
Fixed bug #1282840 (lookahead and "|" actions).
Fixed bug #1164852 (yytext() longer than expected with lookahead).
Fixed bug #1065521 (OS/2 Java 1.1.8 Issues).
Fixed bug #421495 (dangerous lookahead check may fail).
Version 4.12
============
Volker Quetschke (vq@openoffice.org)
#i83540# Add parallel building mode, see the MULTI PROCESSING section in
the dmake man page, for native W32 dmake (MSVC 6, and newer and MinGW)
versions.
Version 4.11
============
Yuri Dario (ydario@openoffice.org)
#i81855, CWS os2port01# Port dmake to OS/2.
Volker Quetschke (vq@openoffice.org)
#i81252# Add a new control macro SHELLCMDQUOTE that can be used to add
additional characters before and after the command string if the recipe is
executed using a shell. This macro is used to avoid problems with quoting
when using cmd.exe or command.com.
Volker Quetschke (vq@openoffice.org)
#i81296, i64572# Improve dependency handling of prerequisites.
Volker Quetschke (vq@openoffice.org)
#i80687, i66751# Allow the use of .PHONY for %-targets.
Volker Quetschke (vq@openoffice.org)
#i80010, i80009# Fix handling of quoted filenames for :1 :b :d :e :f
and :i macro expansions.
Volker Quetschke (vq@openoffice.org)
#i78776# Add a new function macro $(normpath[,para] data) and a new macro
extension to normalise the given data or macro content. The normalization
is done element-wise (whitespace separated) on the given data. Quotes can
be used to normalize filenames that contain whitespace characters.
On cygwin the result honors the setting of .WINPATH to determine the output
format. If the optional parameter para is given for the function macro its
expanded value is used to override the .WINPATH setting for the output.
Version 4.10 (skipped)
======================
This number was skipped to avoid confusion with Version 4.1, patch level 0
which identified itself as "Version 4.10, PL 0".
Version 4.9
===========
Volker Quetschke (vq@openoffice.org)
#i74700# Add a new special macro OOODMAKEMODE that is used to toggle
OOo build specific behavior. If OOODMAKEMODE is set (i.e. it begins with y)
a possible leading ./ of a path will no longer be removed during target
normalization.
Version 4.8
===========
Volker Quetschke (vq@openoffice.org)
#i73499# Add new .WINPATH attribute to generate Windows style paths (with
regular slashes) instead of the default cygwin style (POSIX) paths for
dmake's dynamic macros.
This attribute is specific for cygwin dmake executables and non-cygwin
environments ignore this attribute. This feature can be used to create DOS
style path parameters for native W32 programs from dynamic macros.
The windows style paths use regular slashes ('/') instead of the usual
windows backslash ('\') as directory separator to avoid quoting problems
(It still is a cygwin dmake feature!) and cygwin as well as native windows
programs should have no problems using this (c:/foo/bar) path
representation.
The affected macros are $@, $*, $>, $?, $<, $&, $^ and $(PWD), $(MAKEDIR)
and $(TMD).
Examples:
Content of $(PWD) without .WINPATH (default): /cygdrive/c/temp
Content of $(PWD) with .WINPATH set: c:/temp
Version 4.7
===========
Volker Quetschke (vq@openoffice.org)
#i71422# Add @@ as a new recipe line property. This new property is a
stronger version of the already existing @ recipe property. The recipe
line and the output (stdout and stderr) of the executed recipe are suppressed
and *NOT* shown on the terminal.
Note: Previously the second @ sign was ignored, that means that using this
new feature doesn't break backwards compatibility but the command output
is naturally not suppressed in older versions.
Volker Quetschke (vq@openoffice.org)
#i70210# Dmake now works correctly with empty dynamic prerequisites.
Volker Quetschke (vq@openoffice.org)
#i70168# Improve dmakes handling of literal $ characters in target and
prerequisite filenames. This was not working before and is working now
but the use of literal $ characters in filenames is still strongly
discouraged. See the man page for details.
Volker Quetschke (vq@openoffice.org)
#i69742# Normalize the pathnames of targets and prerequisites to the shortest
(or most natural, see below for the cygwin case) representation.
Now "./foo", "bar/../foo" and foo are recognized as the same file.
For cygwin this allows the use of target and prerequisite names with DOS
like pathnames with drive letters (with / and \ as possible path seperators)
and cygwin POSIX pathnames. As the internal format uses cygwin's natural
POSIX representation runtime macros will result in POSIX paths.
Version 4.6
===========
Volker Quetschke (vq@openoffice.org)
#i67589# Implement the internal dmake commands noop and echo. These commands
were already existing for the native Windows version but only partially
documented.
Volker Quetschke (vq@openoffice.org)
#i67166# Issue a warning when a previously unset macro (i.e. assumed to be
empty) is used and later set to a different value.
Volker Quetschke (vq@openoffice.org)
#i66567# Issue a warning when .SUFFIXES is used. This special target had no
special meaning (anymore?) and was always (at least since version 4.2)
ignored.
Volker Quetschke (vq@openoffice.org)
#i67025# Fix a bug that was introduced in dmake 4.5 and led dmake to falsely
issue an error if a %-target was defined with the .SILENT attribute and dmake
was started with the -vr (included in -v) verbose flag.
Version 4.5
===========
Volker Quetschke (vq@openoffice.org)
#i66385# Fix the handling of .<suffix> targets. Always treat these targets
as meta targets regardless of the AUGMAKE (-A) status. Previously this was
enabled when the AUGMAKE was *not* set to 'yes' or the -A switch was given.
#i66083# We now stop with an error if AUGMAKE meta targets and regular
targets are used in one rule definition. As the syntax of these target
definitions is slightly different this hints to an error in the makefile,
most probably a misspelled attribute or special target.
#i48087#, #i64869# The parsing of %-target definitions was fixed and
enhanced. Prior to dmake 4.5 only one %-target per target-definition worked
reliably, now this works well, but to help projects that still use older
versions a warning was added.
It's not very nice to issue a warning for something that works now but
didn't before. This was only done to aid development and will probably
be removed in future versions.
There was, and still is, that for a bug in dmake for %-targets with more
than one (not indirect) prerequisite only the first prerequisite is used.
This will be fixed in future versions but until this happens we issue a
warning that prerequisites are ignored.
#i65122# The :| rule operator was handled differently from what the man
page said. The man page was adapted to reflect reality. Changing dmakes
behavior to match the man page would have introduced a lot of compatibility
issues.
Version 4.4
===========
2006/02/03 Volker Quetschke (vq@openoffice.org)
#i61170# Fix the TMD macro. Up to now the TMD macro appended a directory
separator if it ended in "..", but most of the time it was not set correctly
at all and/or without a trailing slash.
Note: If your application relies on TMD please check the dmake manual page
for its definition and fix your makefiles if needed.
2006/02/01 Volker Quetschke (vq@openoffice.org)
#i60948# Add -m option family to generate timing information for targets
and/or recipes.
2005/09/19 Volker Quetschke (vq@openoffice.org)
#i53148# Fix $(shell ...) macro picking up the output of earlier
recipe lines in parallel builds.
#i54766# Ensure that all previous recipe lines to a recipe
line containing a $(shell ...) macro have finished before executing
the macro in parallel builds.
2005/06/01 Volker Quetschke (vq@openoffice.org)
#i39248# Add a testsuite to test some dmake features (only for autotools
builds). Start the tests with "make check".
2005/04/21 Volker Quetschke (vq@openoffice.org)
#i47851# Increase the version number to 4.4-cvs and slightly rearrange the
output of "dmake -V".
Remove the hard-coded (in autotools builds) OS macro. It had the wrong value
to be usable with the startup/*.mk and is not mentioned in the man page.
Clean up configure.in and friends.
2005/04/20 Volker Quetschke (vq@openoffice.org)
#i43310# Fix percent (%) rules to recognize prerequisites that are defined
with the multiple target rule operator (::).
This implicitly fixes the similar problem for .<suffix>.<suffix> targets.
2005/04/16 Volker Quetschke (vq@openoffice.org)
#i46987# Fix the documentation of the $(mktmp ...) function macro. This is
not necessarily a new feature as the macro works this way since dmake was
imported into the OpenOffice.org cvs but mentioning it here might help users
of dmake upgrading from very old versions.
Add the "map escape codes" $(...:m) macro expansion that allows to expand
escape codes in macros. It can also be used to reproduce the former (pre
OpenOffice.org cvs) $(mktmp ...) behavior.
2005/04/10 Volker Quetschke (vq@openoffice.org)
#i43252# Introduce the macro ABSMAKECMD that's value for a native Windows
dmake executable (compiled with MS Visual C++ or MinGW) is the absolute
filename and NULL for other operating systems or dmake build with other
compilers.
If DMAKEROOT is not changed and only for native Windows dmake versions the
value of DMAKEROOT now defaults to "$(ABSMAKECMD:d)startup".
This allows to use the startup files from the startup directory from the
same location where the dmake.exe is located.
2005/04/08 Steve Hay (shay@openoffice.org)
#i43241# Fix build problems with VC++ (in non-OOo environment) and fix
the dmake makefiles so that dmake can rebuild itself (VC++ only).
2005/03/14 Volker Quetschke (vq@openoffice.org)
#i44959# Fix problems when a continued line is followed by an empty
or comment line.
2005/03/13 Volker Quetschke (vq@openoffice.org)
#i37053# Fix function macro problems with continued lines.
2004/11/23 Volker Quetschke (vq@openoffice.org)
#i37491# Predefine dmake macro containing one space (SPACECHAR).
2004/11/21 Volker Quetschke (vq@openoffice.org)
#i36027# Improve function macro parameter parsing.
Version 4.3
===========
2004/10/07 Volker Quetschke (vq@openoffice.org)
#i34746# Fix timestamp of phony targets with prerequisites.
2004/07/11 Volker Quetschke (vq@openoffice.org)
#i31255# Add verbose recipe echoing option (-vr).
2004/07/06 Volker Quetschke (vq@openoffice.org)
#i30779# Fix to allow dmake to echo recipe lines when inference is used
to create files that are to be read by .INCLUDE.
2004/04/01 Michael Meeks (mmeeks@openoffice.org)
#i27319#, #i27981# Don't handle environment variables that begin with a
'!', they are used by Cygwin internally and confuse dmake.
2004/01/09 Dan Williams (fa@openoffice.org)
#i17992# Allows the nesting of expressions and a much more complex syntax
for dmake. It is now possible to nest expressions with () and any
combination of || and &&.
Example:
.IF (("$(OS)"=="MACOSX"&&"$(COM)"=="GCC")||"$(OS)"=="LINUX") && "$(GUIBASE)"=="unx"
...
.ENDIF
2003/10/19 Ken Foskey (waratah@openoffice.org)
#i20504# Correct processing of .LIBRARY targets.
2003/10/08 Chris Halls (haggai@openoffice.org)
#i7800# Fix tempnam security problem.
2003/03/08 Volker Quetschke (vq@openoffice.org)
#i10910# Use the build-in tempnam function for MS VC6.
2003/03/05 Volker Quetschke (vq@openoffice.org)
#i11861# Switch to newer autotools autoconf 2.5x and automake 1.5 and
add MinGW and MSVC to the configure buildable targets.
2002/10/11 Ken Foskey (waratah@openoffice.org)
Fix the "lost a child" problem. (Part II)
2002/10/04 Ken Foskey (waratah@openoffice.org)
Rework the configure process.
2002/04/10 Hans-Joachim Lankenau (hjs@openoffice.org)
Don't search INCLUDEDIRS if the filename to be included starts at fs-root.
2001/05/29 Patrick Luby (pluby@openoffice.org)
Added forceful exit to avoid infinite loop that sometimes occurs when
there is a fatal error. Lost a child problem. (Part I)
Version 4.2
===========
(Note, the dmake -V output was not changed and still said
"Version 4.10, PL 0". This probably should have been 4.1)
2001/04/20 Martin Hollmichel (mh@openoffice.org)
First autoconfiscation of dmake.
2001/02/13 Hans-Joachim Lankenau (hjs@openoffice.org)
Fix for leaving tmpfiles when building group targets.
2000/09/22 Jens-Heiner Rechtien (hr@openoffice.org)
Initial import of dmake into OpenOffice.org cvs
before 2000/09/22 ?
Add smaller/greater arithmetic for .IF conditions.
1999/03/18 Hans-Joachim Lankenau (hjs@openoffice.org)
Implement boolean expression "or".
kamel.derouiche@gmail.com
The greenlet package is a spin-off of Stackless, a version of CPython that
supports micro-threads called "tasklets". Tasklets run pseudo-concurrently
(typically in a single or a few OS-level threads) and are synchronized with data
exchanges on "channels".
A "greenlet", on the other hand, is a still more primitive notion of
micro-thread with no implicit scheduling; coroutines, in other words. This is
useful when you want to control exactly when your code runs. You can build
custom scheduled micro-threads on top of greenlet; however, it seems that
greenlets are useful on their own as a way to make advanced control flow
structures. For example, we can recreate generators; the difference with
Python's own generators is that our generators can call nested functions and the
nested functions can yield values too. Additionally, you don't need a "yield"
keyword. See the example in tests/test_generator.py.
Greenlets are provided as a C extension module for the regular unmodified
interpreter.
Greenlets are lightweight coroutines for in-process concurrent programming.
2.0.20:
* Require glib 2.4, and change use of the _take_ownership functions
to _take_ functions
* Support for GTK3 (Pedro L. Lucas)
* names on properties and signals (Pedro L. Lucas)
New in 1.14.1:
* Bugs fixed:
- The user is no longer allowed to override the --srcdir nor the --prefix
configure options used by "make distcheck" (bug#14991).
- Fixed a gross inefficiency in the recipes for installing byte-compiled
python files, that was causing an O(N^2) performance on the number N of
files, instead of the expected O(N) performance. Note that this bug
was only relevant when the number of python files was high (which is
unusual in practice).
- Automake try to offer a more reproducible output for warning messages,
in the face of the newly-introduced randomization for hash keys order
in Perl 5.18.
- The 'test-driver' script now actually error out with a clear error
message on the most common invalid usages.
- Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
#14760, #14911, #15181, #15237).
* Documentation fixes:
- Fixed typos in the 'fix-timestamp.sh' example script that made it
nonsensical.
Changes since 2.2.9:
2008-03-11 david <indent@isidore-it.eu>
* Re-baselined to the FreeBSD indent version to avoid onerous constraints in the old BSD license.
* Release version 2.2.10
2007-12-11 david <indent@isidore-it.eu>
* Added GPL version 3 as the COPYING file.
* Added missing documentation of blf and brf as reported by Tom Tromey <tromey@redhat.com>
2007-11-27 Matthew Wilcox <matthew@wil.cx>
* extended --indent-label with negative offsets. -il0 now
gives no indentation, -il-2 is the default to match the old
behaviour.
2007-11-11 Jean-Christophe Dubois <jcd@tribudubois.net>
* added --indent-label and --linux-style options.
2007-02-25 david Ingamells <david@ingamells.eu>
* Added doxygen profile and updated source to be better documented with doxygen.
* Cleanup of code.
2003-09-28 Erik de Castro Lopo <nospam@bogus.example.com>
* indent.c Fixed Bug#212320: --blank-lines-after-procedures does not work
* indent.c Fixed Bug#206785: indent segfaults on the attached file
From ChangeLog:
from ucommon 6.0.6 to 6.0.7
- error state in fsys open fixed
- fsys error reset inline added
from ucommon 6.0.5 to 6.0.6
- small cleanup of useless validator assignments
- fix gnutls casting and warnings
- modernized automake support
would be sent from Transifex when using old transifex-client.
Here is some of changes from commit log.
* Use urllib3 for the API call; it allows to have proper SSL certificate
verification (see CVE-2013-2073) as well as drop a lot of code.
* Add --psuedo option.
