From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] postsync: skip hooks and metadata-transfer when appropriate (bug 564988)
Date: Fri, 6 Nov 2015 09:24:15 -0800 [thread overview]
Message-ID: <563CE23F.9050604@gentoo.org> (raw)
In-Reply-To: <563C62DD.4010303@gentoo.org>
On 11/06/2015 12:20 AM, Alexander Berntsen wrote:
> On 06/11/15 09:05, Michał Górny wrote:
>>>> I know nothing about the egencache stuff. Maybe Michał can
>>>> comment?
>> Michał finds this black magic. Trusts zmedico.
> I think it looks like it's probably supposed to be reasonable, perhaps.
>
> Maybe Brian can look at it. At least that way we'll have a lot of
> people that attempted understanding what's going on.
>
> Maybe we need a "Trusted-by:" line.
>
Maybe it helps if I give some more context. At my workplace, we have
lots of scripts that call `emerge --sync private-work-repo` to ensure
that the current system has the latest changes from private-work-repo.
It can be annoying if it spends the bulk of its time calling hooks, even
though private-work-repo was already up-to-date:
>>> Timestamps on the server and in the local repository are the same.
>>> Cancelling all further sync action. You are already up to date.
So, we want to skip the hooks when repos are already up-to-date. In this
case, there's no point in calling hooks or updating the metadata cache.
--
Thanks,
Zac
next prev parent reply other threads:[~2015-11-06 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 7:44 [gentoo-portage-dev] [PATCH] postsync: skip hooks and metadata-transfer when appropriate (bug 564988) Zac Medico
2015-11-06 7:50 ` Alexander Berntsen
2015-11-06 8:05 ` Michał Górny
2015-11-06 8:20 ` Alexander Berntsen
2015-11-06 17:24 ` Zac Medico [this message]
2015-11-06 18:39 ` Michał Górny
2015-11-06 18:58 ` Zac Medico
2015-11-06 19:34 ` Michał Górny
2015-11-06 19:49 ` Zac Medico
2015-11-06 20:19 ` Michał Górny
2015-11-06 20:28 ` Zac Medico
2015-11-06 18:54 ` Brian Dolbec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=563CE23F.9050604@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox