| 1 |
On Mon, 21 Jul 2014 23:15:41 +0200 |
| 2 |
Jeroen Roovers <jer@g.o> wrote: |
| 3 |
> On Mon, 21 Jul 2014 23:06:07 +0200 |
| 4 |
> Pacho Ramos <pacho@g.o> wrote: |
| 5 |
> > Maybe this could be solved by having two kinds of revisions: |
| 6 |
> > - One would rebuild all as usually (for example, -r1...) |
| 7 |
> > - The other one would only regenerate VDB and wouldn't change the |
| 8 |
> > installed files (for example, -r1.1) |
| 9 |
> |
| 10 |
> Or the package manager looks at changed in *DEPEND between the repo |
| 11 |
> and vdb and resolves those. |
| 12 |
|
| 13 |
...assuming that the ebuild hasn't been removed, and that it can be |
| 14 |
associated correctly when overlays are involved, and that the change |
| 15 |
wasn't a change where a saved pkg_prerm uses the old dependency, not |
| 16 |
the new one, or all the other ways this breaks. |
| 17 |
|
| 18 |
You need to think your cunning plan the whole way through. |
| 19 |
|
| 20 |
-- |
| 21 |
Ciaran McCreesh |
Archives