On Mon, Sep 3, 2018 at 10:41 AM Alexander Larsson wrote:
>
> On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
> >
> > Valid point - I forgot about that.
> >
> > A couple of ideas come to mind:
> > - static link LLVM (Flatpak already does it)
> > No L
very simple workaround, can you add the file sizes (as well
as the mtimes) to the staleness check? I mean, its possible that a
rebuild generates the exact same size, but at least its better than
always being wrong.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Fri, Aug 31, 2018 at 11:57 AM Timothy Arceri wrote:
>
> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
> We depend on build timestamps of the mesa/llvm binaries when generating
> the sha for cache items. So if flatpak results in two versions of mesa
> having the same timestamp then there is
that work? Is this fixed somewhere with a patch i can backport?
And if not, do we need to add some magic to flatpak to automatically
clean up the shader cache after an update?
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander LarssonRed Hat, Inc
