| 1 |
On Fri, 16 Apr 2010 22:30:46 -0500 |
| 2 |
Steev Klimaszewski <steev@g.o> wrote: |
| 3 |
> On Fri, Apr 16, 2010 at 3:28 PM, Ciaran McCreesh |
| 4 |
> <ciaran.mccreesh@××××××××××.com> wrote: |
| 5 |
> > On Fri, 16 Apr 2010 16:23:48 -0400 |
| 6 |
> > James Cloos <cloos@×××××××.com> wrote: |
| 7 |
> >> OK. Let me rephrase. Portage does not need to validate local |
| 8 |
> >> changes. |
| 9 |
> > |
| 10 |
> > Sure it does. If it doesn't, and your local changes affect metadata, |
| 11 |
> > horrible things happen. |
| 12 |
> |
| 13 |
> Why not check the mtime on the overlay, if it is older than last sync |
| 14 |
> time, not invalid. |
| 15 |
|
| 16 |
Because it can still be invalid if you do that. If you're using a repo |
| 17 |
with pregenerated cache with an eclass from a different repo than the |
| 18 |
one used do the pregenerating, the pregenerated cache is always invalid. |
| 19 |
|
| 20 |
> >> If a user uses a local eclass to override one in portage or in some |
| 21 |
> >> remote overlay s/he follows, it is his/er responsibility to update |
| 22 |
> >> it when the original undergoes major renovation. |
| 23 |
> > |
| 24 |
> > Users aren't responsible... |
| 25 |
> |
| 26 |
> And doing everything we can to make them not be isn't going to teach |
| 27 |
> them anything. |
| 28 |
|
| 29 |
Which is why you design a system that just gets things right, rather |
| 30 |
than one that relies upon users getting things right. |
| 31 |
|
| 32 |
-- |
| 33 |
Ciaran McCreesh |
Archives