1 |
On Sun, 31 Aug 2008 15:38:43 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
|
4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
5 |
> Hash: SHA1 |
6 |
> |
7 |
> Hi everyone, |
8 |
> |
9 |
> Please consider a blocker syntax extension, for inclusion in EAPI 2, |
10 |
> which will serve to indicate that conflicting packages may be |
11 |
> temporarily installed simultaneously when upgrading or installing a |
12 |
> series of packages. When temporary simultaneous installation of |
13 |
> conflicting packages occurs, the installation of a newer package may |
14 |
> overwrite any colliding files that belong to an older package which |
15 |
> is explicitly blocked. When such a file collision occurs, the |
16 |
> colliding files will cease to belong to the older package, and they |
17 |
> will remain installed after the older package is eventually |
18 |
> uninstalled. The older package will be uninstalled only after any |
19 |
> newer blocking packages have been merged on top of it. I have |
20 |
> written a blog entry [1] which shows some specific examples of this |
21 |
> process in action. |
22 |
|
23 |
If a file overwritten by the second package falls under CONFIG_PROTECT, |
24 |
will portage treat it like a normal update? |
25 |
|
26 |
|
27 |
-- |
28 |
gcc-porting, by design, by neglect |
29 |
treecleaner, for a fact or just for effect |
30 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |