| 1 |
On 11/06/2015 12:20 AM, Alexander Berntsen wrote: |
| 2 |
> On 06/11/15 09:05, Michał Górny wrote: |
| 3 |
>>>> I know nothing about the egencache stuff. Maybe Michał can |
| 4 |
>>>> comment? |
| 5 |
>> Michał finds this black magic. Trusts zmedico. |
| 6 |
> I think it looks like it's probably supposed to be reasonable, perhaps. |
| 7 |
> |
| 8 |
> Maybe Brian can look at it. At least that way we'll have a lot of |
| 9 |
> people that attempted understanding what's going on. |
| 10 |
> |
| 11 |
> Maybe we need a "Trusted-by:" line. |
| 12 |
> |
| 13 |
|
| 14 |
Maybe it helps if I give some more context. At my workplace, we have |
| 15 |
lots of scripts that call `emerge --sync private-work-repo` to ensure |
| 16 |
that the current system has the latest changes from private-work-repo. |
| 17 |
It can be annoying if it spends the bulk of its time calling hooks, even |
| 18 |
though private-work-repo was already up-to-date: |
| 19 |
|
| 20 |
>>> Timestamps on the server and in the local repository are the same. |
| 21 |
>>> Cancelling all further sync action. You are already up to date. |
| 22 |
|
| 23 |
So, we want to skip the hooks when repos are already up-to-date. In this |
| 24 |
case, there's no point in calling hooks or updating the metadata cache. |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives