public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Yonghong Zhu <yonghong.zhu@intel.com>, edk2-devel@lists.01.org
Cc: Michael Kinney <michael.d.kinney@intel.com>,
	Kevin W Shaw <kevin.w.shaw@intel.com>,
	Liming Gao <liming.gao@intel.com>
Subject: Re: [Patch V2] Build spec: add description for build with binary cache
Date: Thu, 28 Sep 2017 14:13:57 +0200	[thread overview]
Message-ID: <04e10841-f112-e2eb-2188-dd930178e150@redhat.com> (raw)
In-Reply-To: <0dbfc584-f13c-c712-0ef5-bf1741b89bcd@redhat.com>

On 09/28/17 14:06, Laszlo Ersek wrote:

> So, how can I invalidate all the cached values? Is it enough to delete
> the *.hash files?

... I'm asking because I tried the --binary-destination option as well,
and in the bin cache directory, *.depex and *.inf files were stored as
well, not just *.hash values.

So I figure, whatever gets stored in the binary cache directory, should
be deleted when I'd like to invalidate the cache.

Now, removing this separate cache directory altogether would solve my
question; but that would require me to use "--binary-destination" and
"--binary-source" together. The idea is that "--hash" would fetch the
hash values from that separate directory, and it would also write the
new hash values back to that directory. In addition this directory would
be very easy to remove, so "--hash" would know whenever the hash was empty.

However, it looks like "--binary-destination" and "--binary-source"
cannot be used together. Why is that?

Thanks,
Laszlo


  reply	other threads:[~2017-09-28 12:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19  6:48 [Patch V2] Build spec: add description for build with binary cache Yonghong Zhu
2017-09-27  7:20 ` Gao, Liming
2017-09-28  8:19 ` Laszlo Ersek
2017-09-28  9:02   ` Gao, Liming
2017-09-28 11:15     ` Laszlo Ersek
2017-09-28 11:28       ` Gao, Liming
2017-09-28 12:06 ` Laszlo Ersek
2017-09-28 12:13   ` Laszlo Ersek [this message]
2017-09-30  5:03     ` Gao, Liming
2017-09-30  5:14       ` Ni, Ruiyu
2017-09-30  2:49   ` Gao, Liming
2017-09-30 21:20     ` Laszlo Ersek

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-list 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=04e10841-f112-e2eb-2188-dd930178e150@redhat.com \
    --to=devel@edk2.groups.io \
    /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