Changes in 3.0 include:
* The www-exp module has been renamed webui, and a new web frontend has
been added called paefchen.
* All Tinderbox commands with the exception of tinderd are now performed
using the tc utility.
* The Hosts system has been removed as it was not really used, and not
really suited to the purpose of distributed builds. The ground work has
been laid to support distributed builds, but that is not present in 3.0.
* A DISTFILE_URI config directive has been introduced to allow for
distributed distfile caches.
* The latest port fail reasons and patterns have been synced from
pointyhat.
* The total size taken by a port build (in KB) is now tracked in the
database. This can be obtained using the command ``tc getPortTotalSize
-d DIRECTORY -b BUILD''.
* Port build logs now contain OPTIONS and environment details.
* The ``tc addPort'' command assumes a recursive add by default. This
can be disabled by passing the -R argument.
* Port dependencies are now recorded in the database when ``tc addPort''
is called without -R. The dependency list can be retrieved with ``tc
getDependenciesForPort -d DIRECTORY -b BUILD''.
* The ``tc tbcleanup'' command now supports pruning stale distfiles,
stale packages, and not pruning old error logs. See the README for
command line details.
* The default update type and update host are configurable at Setup and
Upgrade time. The default update type has been changed from CVSUP to
CSUP.
* The last_fail_reason is now exported to the postPortBuild Hook.
* Fix the build time display if a tinderbuild takes longer than 24 hours.
* Add a new command, ``tc rescanPorts'' which updates the properties of
all ports in the datastore (including dependencies).
* Display the remake count in the webui frontends.
* Hack around a potential perl-related leftover false positive.
* A new -O option has been added to addPort/rescanPorts which enables
OPTIONS, but does not run rmconfig before calling config. This way,
existing OPTIONS can be preserved. The default behavior is to call
rmconfig to maintain POLA.
* The webui index page has been enhanced to make it more readable, and
more powerful.
* The number of ports not built due to dependency failures has been
added to the webui's main page.
* tc processLog -v now prints the matching text to aid with false
positive identification.
PLUS:
* In webui:
- Change tinderd queue view. Field for adding new ports is the first now.
- Show target port of current build.
- miwi's RSS module
- an other patch from miwi for inc_tinderbox.php.dist which should make
setting-up the webui easier on non-standard configurations.
* Bug-fix: Add o and O to the list of valid options for addPort.
installation.
COPYTREE_* macros install files with cpio -dumpl (l -- hardlink) and
then do chmod & chown against the newly installed files, so when
WRKSRC and PREFIX are under the same filesystem, permissions of the
original files under the working directory are also affected. That
was how installing files with wrong permissions caused make test under
the working directory to fail.
management, connection management, and an HTTP/1.1 compliant HTTP agent
implementation based on those components. It is intended as successor of
and replacement for Jakarta Commons HttpClient 3.x.
The HttpClient module is a full-featured, HTTP/1.1 compliant agent built
on top of HttpCore.
The HttpMime module extends mime4j library with some HTTP specific
functionality and integrates it with the HttpComponents framework.
WWW: http://hc.apache.org/httpcomponents-client/
protocol. They are nonetheless sufficient to develop basic client-side and
server-side HTTP services with a minimal footprint and no external
dependencies.
The HttpCore base module contains the public API and the default
implementation based on the Java classic (blocking) I/O model. It requires
a Java 1.3 compatible runtime and has no dependency on any external libraries.
HttpCore NIO extensions contain optional components that leverage the event
driven, non-blocking I/O (NIO) model. HttpCore NIO extensions require a
Java 5.0 compatible runtime and the HttpCore base module. HttpCore NIO
extensions are intended for those usage scenarios where raw throughput is
less important than the ability to handle thousands of simultaneous HTTP
connections in a resource efficient manner.
WWW: http://hc.apache.org/httpcomponents-core/
in plain rfc822 and MIME format. The parser uses a callback mechanism to
report parsing events such as the start of an entity header, the start
of a body, etc. If you are familiar with the SAX XML parser interface
you should have no problem getting started with mime4j.
The parser only deals with the structure of the message stream. It won't
do any decoding of base64 or quoted-printable encoded header fields and
bodies.
The parser has been designed to be extremely tolerant against messages
violating the standards.
mime4j can also be used to build a tree representation of an e-mail
message using the Message class. Using this facility mime4j
automatically handles the decoding of fields and bodies and uses
temporary files for large attachments.
WWW: http://james.apache.org/mime4j/
- Add a small patch that gets rid of the "ordering CD from..." sleeps,
speeding up initial configure time
Update requested by: Terry Kennedy <terry@tmk.com>
The new code will silently ignore MASTER_SITE_GOOGLE_CODE and
MASTER_SITE_DEBIAN_POOL unless specifically asked to sort them, in which
case an error message is printed.
Most of the patch came from Ryan Steinmetz <rpsfa@rit.edu> with small
additions by me.
