the JDK/JRE ports. This will make keeping up to date with new timezone
data easier and prevent all the JDK/JRE ports needing to be updated
regularly whenever a new TZUpdater is released by Oracle.
Feature safe: yes
Role composition can be thought of as much more clever and meaningful multiple
inheritance. The basics of this implementation of roles is:
- If a method is already defined on a class, that method will not be composed in
from the role.
- If a method that the role "requires" to be implemented is not implemented,
role application will fail loudly.
Unlike Class::C3, where the last class inherited from "wins," role composition
is the other way around, where first wins. In a more complete system (see Moose)
roles are checked to see if they clash. The goal of this is to be much simpler,
hence disallowing composition of multiple roles at once.
WWW: http://search.cpan.org/dist/Role-Tiny/
Feature safe: yes
- switch to GOOGLE_CODE as distfiles mirror
- switch to USE_XZ
- add two upstream patches (patch-rtengine-CA__correct__RT.c and
patch-rtengine_array2D.h) [1]
to fix build on i386. They should be removed after release of 4.0.8.
- add patch (patch-rtengine_improcfun.h) to fix build on log2()-less systems
(~everything<=8.3)
- some cosmetics
It would be great if someone with access to ia64, powerpc, sparc64 could confirm
that it still failing there.
[1] http://code.google.com/p/rawtherapee/source/detail?r=4b5ae9eb4000ce5eb8e8939343da4d8f4ee4a36d
Feature safe: yes
- pass maintainerhship to submitter
- broken on < 900000
- while here drop WWWDIR_REL in favor of WWWDIR and use PORTDOCS
PR: ports/165211
Submitted by: pakhom706@gmail.com
Feature safe: yes
originally for the Commodore 64 and released in 1984
By Broderbund and written by Ed Hobbs.
PR: ports/158781
Submitted by: Robert Crossfield <robcrossfield@gmail.com>
Approved by: itetcu (mentor)
Feature safe: yes
- changes:
* query -f has been replaced by query -F when querying a package (file) for consistency with pkg info
* fix autoremove recursion
* pkg set -o oldorigin:neworigin allow the user to modify the origin of a packages (useful for MOVED)
* several fixes on powerpc
* pkg query evaluation expression now accept !=
* pkg2ng is now able to migrate a local database without needed the ports tree
* speed up pkg check by only loading the informations needed for the operation it will do
* code cleanup in the library
* fix uname/gname lookup when creating packages
* new periodic script for pkg audit
* new keyword shlib, pkgng is able to load information about the needed shlibs for a package (disable by default)
* pkg info act as pkg info -a by default
* new install timestamp in the package database, available using pkg query "%t"
* pkg updating can now take a port name as argument to only show related UPDATING informations)
* -q (quiet) for install, delete, upgrade, update and autoremove
* new ABI detection string
Concerning the new ABI, to be able to determine which package can be installed on which destination, pkgng couldn't rely on the simple:
os version/machine, because some arches have incompatible ABIs. Can compute on its own the ABI, the string is the followin:
OSNAME:OSMAJORVERSION:OSARCH:OSCLASS(:...)
... means the arch specific extensions.
which means on:
* amd64: freebsd:9:x86:64
* i386: freebsd:9:x86
* arm: freebsd:9:arm:eb:oabi:softvp
etc
Be careful all the packages (.txz) files have to be rebuilt!!!
When binary upgradeing from pkg beta8, on amd64 do the following:
UNAME_m=freebsd:9:x86:64 pkg install -f pkg
on i386
UNAME_m=freebsd:9:x86:32 pkg install -f pkg
Bonus when run on a chroot/jail where ABI is different from the host, pkgng will dynamically determine the destination ABI.
Feature safe: yes
