| 1 |
On Sat, 26 Jul 2014 18:36:27 +0000 (UTC) |
| 2 |
Martin Vaeth <martin@×××××.de> wrote: |
| 3 |
> Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 4 |
> >> > * Overlays |
| 5 |
> >> Not an issue: Exactly the information of that ebuild |
| 6 |
> >> which *would* be used if you reemerge contains |
| 7 |
> >> the relevant data. |
| 8 |
> > |
| 9 |
> > The association between an installed package and "the ebuild it came |
| 10 |
> > from" doesn't work correctly when overlays around. |
| 11 |
> |
| 12 |
> It doesn't have to: That ebuild which would be installed |
| 13 |
> *has* to carry the up-to-date information for that package. |
| 14 |
> Otherwise, the overlay is broken. An overlay is *not* a |
| 15 |
> different slot for a package. |
| 16 |
|
| 17 |
Uh huh, so you add an overlay, and suddenly the dependencies for a |
| 18 |
random subset of your installed packages change in ways that don't in |
| 19 |
any way reflect what you have installed. How is this the desired |
| 20 |
behaviour? |
| 21 |
|
| 22 |
-- |
| 23 |
Ciaran McCreesh |
Archives