Re: [Buildroot] [PATCH 2/2] package/pkg-hare: move cache directory outside of $(HOME)

From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org,  Francois Perrad <francois.perrad.86@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/pkg-hare: move cache directory outside of $(HOME)
Date: Tue, 20 Oct 2026 15:17:10 +0200	[thread overview]
Message-ID: <atdo86oTqhAX5Oes@windsurf> (raw)
In-Reply-To: <8b5cbb21-caa0-4935-b2d4-35908b5ab0d8@gmx.de>

On Tue, Oct 20, 2026 at 02:55:04PM +0200, Fiona Klute wrote:
> Am 20.10.26 um 14:06 schrieb Thomas Petazzoni via buildroot:
> > By default, hare will store its cache directory in $(HOME)/.cache,
> > which is a problem as we don't want a Buildroot build to write outside
> > of its output directory (to the exception of DL_DIR, of course). The
> 
> And CCACHE_DIR, if enabled. Not really critical, but might give someone
> who's new to Buildroot a wrong idea. ;-)

True.

> I'm not familiar with Hare, what does it store in its cache dir? The default
> path suggests it's intended as a global cache, so I'm wondering if something
> like $(BUILD_DIR)/.hare-cache might be better than a per-package cache. But
> of course that depends on what goes in there.

I must say I'm not sure. On the package/hare patch, I asked the
feedback from François Perrad precisely for this reason. For what I
can see, it contains "object files" for each source file that has been
compiled, along with a bunch of other things.

See:

  https://paste.ack.tf/3839b9@raw

(from this I can see the path within
output/build/hare-dbus-e9a89f8bc5ce783fa25f0eb67d7d8932db90bcc2/.cache
seems a bit crazy though.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot