root/releases/pkgcore/0.1.1/NOTES @ ferringb%2540gentoo.org-20061003002842-9919f5fcf9ae85f2

Revision ferringb%2540gentoo.org-20061003002842-9919f5fcf9ae85f2, 2.2 kB (checked in by Brian Harring <ferringb@…>, 2 years ago)

0.1.1 release notes.

Line 
1Release Notes:
2
3  See ChangeLog for full commit logs.
4
5pkgcore 0.1.1:
6
7  * hang fix for test_filter_env
8 
9  * package.keywords fixes: no longer incremental, supports '*' and '~*'
10    properly
11 
12  * FEATURES="userpriv" support works again.
13 
14  * pmerge repository ordering now behaves properly; prefers src ebuilds, then
15    built pkgs; -k inverts that (previously was semi-undefined)
16 
17  * binpkg fixes: run setup phase
18 
19  * replace op fixes: force seperate WORKDIR for unmerge to protect against
20    env collisions
21 
22  * loosened category rules: allow _. chars to support cross-dev hack.
23 
24  * build fixes: make $A unique to avoid duplicate unpacks; force distdir
25    creation regardless of whether or not the pkg has any stated SRC_URI
26    (fixes cvs and subversion eclsas usage).  Fix sandbox execution to chdir
27    to an existant directory (sandbox will fail if ran from a nonexistant dir).
28 
29  * change DelayedInstantiation objects to track __class__ themselves; this
30    fixes pquery to properly shutdown when ctrl+c'd (previously could swallow
31    the interrupt due to cpython isinstance swallowing KeyboardInterrupt).
32 
33 
34pkgcore 0.1:
35
36  Initial release.
37 
38  * Sync functionality doesn't yet exist (pmaint script will be in 0.2)
39 
40  * pmerge vdb modification requires --force; this will be disabled in 0.2,
41    mainly is in place so that folks who are just looking, don't inadvertantly
42    trigger an actual modification.
43 
44  * not all portage FEATURES are implemented; same for QA.
45 
46  * If overlays are in use, pkgcore may defer to it's a seperate cache to avoid
47    pkgcore causing cache regen for portage (and vice versa); this occurs due
48    to pkgcore treating overlays as their own repo and combining them at a
49    higher level; portage smushes them all together thus rendering each subtree
50    unusable in any standalone fashion.
51
52  * pkgcore is far more anal about blocking bad behaviour in ebuilds during
53    metadata regeneration; tree is clean, but if you do something wrong in
54    global scope, it *will* catch it and block it.
55 
56  * EBD; daemonized ebuild.sh processing (effectively), pkgcore reuses old
57    ebuild.sh processes to avoid bash startup, speeding regen up by roughly
58    2x.
Note: See TracBrowser for help on using the browser.