| Line | |
|---|
| 1 | Release Notes: |
|---|
| 2 | |
|---|
| 3 | See ChangeLog for full commit logs. |
|---|
| 4 | |
|---|
| 5 | pkgcore 0.1: |
|---|
| 6 | |
|---|
| 7 | Initial release. |
|---|
| 8 | |
|---|
| 9 | * Sync functionality doesn't yet exist (pmaint script will be in 0.2) |
|---|
| 10 | |
|---|
| 11 | * pmerge vdb modification requires --force; this will be disabled in 0.2, |
|---|
| 12 | mainly is in place so that folks who are just looking, don't inadvertantly |
|---|
| 13 | trigger an actual modification. |
|---|
| 14 | |
|---|
| 15 | * not all portage FEATURES are implemented; same for QA. |
|---|
| 16 | |
|---|
| 17 | * If overlays are in use, pkgcore may defer to it's a seperate cache to avoid |
|---|
| 18 | pkgcore causing cache regen for portage (and vice versa); this occurs due |
|---|
| 19 | to pkgcore treating overlays as their own repo and combining them at a |
|---|
| 20 | higher level; portage smushes them all together thus rendering each subtree |
|---|
| 21 | unusable in any standalone fashion. |
|---|
| 22 | |
|---|
| 23 | * pkgcore is far more anal about blocking bad behaviour in ebuilds during |
|---|
| 24 | metadata regeneration; tree is clean, but if you do something wrong in |
|---|
| 25 | global scope, it *will* catch it and block it. |
|---|
| 26 | |
|---|
| 27 | * EBD; daemonized ebuild.sh processing (effectively), pkgcore reuses old |
|---|
| 28 | ebuild.sh processes to avoid bash startup, speeding regen up by roughly |
|---|
| 29 | 2x. |
|---|
