| 1 | Release Notes: |
|---|
| 2 | |
|---|
| 3 | See ChangeLog for full commit logs. |
|---|
| 4 | |
|---|
| 5 | |
|---|
| 6 | pkgcore 0.1.3: |
|---|
| 7 | |
|---|
| 8 | * Always process "|| ( a b )" in the right order. |
|---|
| 9 | |
|---|
| 10 | * Fix disabling a flag in package.use.mask or package.use.force. |
|---|
| 11 | |
|---|
| 12 | |
|---|
| 13 | pkgcore 0.1.2: |
|---|
| 14 | |
|---|
| 15 | * Make filter_env work on hppa (and possibly more architectures) where using |
|---|
| 16 | python CFLAGS for this standalone binary does not work. |
|---|
| 17 | |
|---|
| 18 | * Fall back to plain text output if the TERM variable is unsupported. |
|---|
| 19 | |
|---|
| 20 | * Deal with dangling symlinks in binpkg repositories. |
|---|
| 21 | |
|---|
| 22 | * Fix expanding of incrementals (like USE) in make.defaults. |
|---|
| 23 | |
|---|
| 24 | * pquery: support --attr fetchables, handle extra commandline arguments as |
|---|
| 25 | -m or --expr restrictions. |
|---|
| 26 | |
|---|
| 27 | * USE deps once again allow setting a flag only if it is actually settable |
|---|
| 28 | on the target package. |
|---|
| 29 | |
|---|
| 30 | |
|---|
| 31 | pkgcore 0.1.1: |
|---|
| 32 | |
|---|
| 33 | * hang fix for test_filter_env |
|---|
| 34 | |
|---|
| 35 | * package.keywords fixes: no longer incremental, supports '*' and '~*' |
|---|
| 36 | properly |
|---|
| 37 | |
|---|
| 38 | * FEATURES="userpriv" support works again. |
|---|
| 39 | |
|---|
| 40 | * pmerge repository ordering now behaves properly; prefers src ebuilds, then |
|---|
| 41 | built pkgs; -k inverts that (previously was semi-undefined) |
|---|
| 42 | |
|---|
| 43 | * binpkg fixes: run setup phase |
|---|
| 44 | |
|---|
| 45 | * replace op fixes: force seperate WORKDIR for unmerge to protect against |
|---|
| 46 | env collisions |
|---|
| 47 | |
|---|
| 48 | * loosened category rules: allow _. chars to support cross-dev hack. |
|---|
| 49 | |
|---|
| 50 | * build fixes: make $A unique to avoid duplicate unpacks; force distdir |
|---|
| 51 | creation regardless of whether or not the pkg has any stated SRC_URI |
|---|
| 52 | (fixes cvs and subversion eclsas usage). Fix sandbox execution to chdir |
|---|
| 53 | to an existant directory (sandbox will fail if ran from a nonexistant dir). |
|---|
| 54 | |
|---|
| 55 | * change DelayedInstantiation objects to track __class__ themselves; this |
|---|
| 56 | fixes pquery to properly shutdown when ctrl+c'd (previously could swallow |
|---|
| 57 | the interrupt due to cpython isinstance swallowing KeyboardInterrupt). |
|---|
| 58 | |
|---|
| 59 | |
|---|
| 60 | pkgcore 0.1: |
|---|
| 61 | |
|---|
| 62 | Initial release. |
|---|
| 63 | |
|---|
| 64 | * Sync functionality doesn't yet exist (pmaint script will be in 0.2) |
|---|
| 65 | |
|---|
| 66 | * pmerge vdb modification requires --force; this will be disabled in 0.2, |
|---|
| 67 | mainly is in place so that folks who are just looking, don't inadvertantly |
|---|
| 68 | trigger an actual modification. |
|---|
| 69 | |
|---|
| 70 | * not all portage FEATURES are implemented; same for QA. |
|---|
| 71 | |
|---|
| 72 | * If overlays are in use, pkgcore may defer to it's a seperate cache to avoid |
|---|
| 73 | pkgcore causing cache regen for portage (and vice versa); this occurs due |
|---|
| 74 | to pkgcore treating overlays as their own repo and combining them at a |
|---|
| 75 | higher level; portage smushes them all together thus rendering each subtree |
|---|
| 76 | unusable in any standalone fashion. |
|---|
| 77 | |
|---|
| 78 | * pkgcore is far more anal about blocking bad behaviour in ebuilds during |
|---|
| 79 | metadata regeneration; tree is clean, but if you do something wrong in |
|---|
| 80 | global scope, it *will* catch it and block it. |
|---|
| 81 | |
|---|
| 82 | * EBD; daemonized ebuild.sh processing (effectively), pkgcore reuses old |
|---|
| 83 | ebuild.sh processes to avoid bash startup, speeding regen up by roughly |
|---|
| 84 | 2x. |
|---|
