https://sourceware.org/bugzilla/show_bug.cgi?id=30221
--- Comment #8 from Vicki Pfau ---
Apologies for the double-post of the first part of that comment. I reloaded the
page and apparently hitting the reply button didn't clear the comment at the
top and I didn't notice until I replied.
--
You a
https://sourceware.org/bugzilla/show_bug.cgi?id=30221
--- Comment #7 from Vicki Pfau ---
I have a proof of concept patch that I can attach here or submit to the mailing
list if you think the xattrs approach is a good way to go. Alternatively, a
metadata directory could be added under each buildid
https://sourceware.org/bugzilla/show_bug.cgi?id=30221
--- Comment #6 from Frank Ch. Eigler ---
(In reply to Vicki Pfau from comment #2)
> 404 and the like *may* be transient, but the fact of the matter is that
> *most* of the time it won't be And it's a cache, not a definitive answer
> saying thi
https://sourceware.org/bugzilla/show_bug.cgi?id=30221
--- Comment #5 from Vicki Pfau ---
I have a proof of concept patch that I can attach here or submit to the mailing
list if you think the xattrs approach is a good way to go. Alternatively, a
metadata directory could be added under each buildid
https://sourceware.org/bugzilla/show_bug.cgi?id=30221
--- Comment #4 from Frank Ch. Eigler ---
(In reply to Vicki Pfau from comment #3)
> I have a proof of concept patch that I can attach here or submit to the
> mailing list if you think the xattrs approach is a good way to go.
> Alternatively, a
https://sourceware.org/bugzilla/show_bug.cgi?id=30221
--- Comment #3 from Vicki Pfau ---
I have a proof of concept patch that I can attach here or submit to the mailing
list if you think the xattrs approach is a good way to go. Alternatively, a
metadata directory could be added under each buildid
