Pkgcore

---------------------------

- ticket 235; CBUILD/CTARGET values were being stomped w/ CHOST.

- EAPI=3 support; pkgcore already preserved mtimes at the second level,
remaining bits were added for full EAPI3 support.

Pkgcore doesn't currently fully PREFIX offset merges, but that will be
added in the next release or two most likely.

- EBUILD_PHASE was set to setup-binpkg for pkg_setup phase w/ binpkgs-
ebuilds expected setup however, thus EBUILD_PHASE is now set to setup
always for pkg_setup phase.

- fixup env filtering- backslash escaping wasn't needed in the patterns
resulting in failed matches. Mostly protective cleanup.

- tweak cache backend to not stamp cache entries where mtime is no longer
external w/ an mtime of '-1'. Didn't hurt anything but was a pointless op.

- fix the cpy incremental_expansion implementation; not sure how it slipped
in being slower then native python, but the cpy version is now 60% faster
than the native equivalent.
Additionally, this extension is now disabled under py2.4 since it makes
heavy use of PySet apis.

- ticket 234; handle refs properly in dhcpformat/mke2fsformat.

- pkgcore atom objects blocks_temp_ignorable data is now stored in
blocks_strongly; the old attr is aliased, although will be removed.

- pkgcore now supports revisions of arbitrary length (previously was <31 bits).


--------------------------

--------------------------

--------------------------

- >snakeoil-0.3.4 is required for this release.

- key is reused as cpvstr for memory savings where possible in cpv
extension objects.

- cpv extension objects now intern package, category, and key for
memory reduction reasons.

- various slot fixups to reduce memory usage and potential corner case
bugs.

- fix the scenario where there is one repo returned from the domain for
pmerge... crappy bug feedback on that one lead to it slipping by.


--------------------------

--------------------------

- added pinspect script; used for basic reporting of metadata usage,
and inspection of pkgsets. Bit simple, but will be expanded down the line.

- filter-env is now installed into PATH; cli api isn't considered stable,
but it should be useful for folks playing w/ bash environments or doing
ebuild inspection.

- correct a tb in pmerge when the user configuration is strictly a single
source repository. Semi rare, but can occur.

- correct a tb when throwing a missing file error for specifying package.*
settings directly to domain.

- correct a tb in profiles expansion code of USE_EXPAND and USE_EXPAND_HIDDEN
when they're completely undefined in the profile stack. Rare, but if a
user is building a custom profile stack from the ground up, it's possible
to hit it.

- gentoo upstream bug 297933; filter BASHOPTS to keep bash 4.1 happy.

- correct an encoding issue in making binpkgs when an ebuild is utf8

- fix a traceback in pmerge -fK when trying to fetch required files for
binpkgs.


--------------------------

--------------------------

- tweak pkgcore configuration subsystem to tell you the parameter involved
when it's passed an incorrectly typed object.

- fix an encoding issue w/ utf8 ebuilds on merging.


--------------------------

--------------------------

- portage changed their flat_hash support a while back, specifically
how mtime was stored. We match that now (although it's daft to do so)
for compatibility sake- primarily affected CVS users.

- removed a potential in the merge engine where triggers that didn't
do an abspath on items they added could incorrectly be moved.
Specifically affected FEATURES=debugedit for /usr/lib -> lib64 pathways.

- boolean restrictions now default to being finalized.

- pkgcore.fs.ops.offset_rewriter -> pkgcore.fs.contents.offset_rewriter

- various code cleanups, quite a few conversions to snakeoil.klass
decorators/property tricks to simplify the code.

- experimental python3.1 support. Bugs welcome, although till stated
otherwise, it's considered unsupported.

- pkgcore.restrictions.values.ComparisonMatch has been removed.

- for overlayed repositories that have invalid atom stacking in their
package.mask, give an appropriate error message indicating the file.

- gentoo bug 196561, PMS doesn't match portage behaviour for '~' atom
operator. Being that the pms definition has never been accurate, and
portage hasn't handled '~' w/ a revision in any sane form, and finally
do to portage adding a repoman check for this (bug 227225) pkgcore is
now strict about disallowing revisions with '~'. Scream at PMS to
fix their doc if it's problematic.

- certain ebuilds (ssmtp for example) expect D to have a trailing '/'.
Force this (outside pms compliance, so we match portage behaviour).


--------------------------