On Sat, Jul 22, 2017 at 1:03 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Sat, Jul 22, 2017 at 11:25:48AM -0600, Chris Murphy wrote: >> > Here you aren't root so it's not using the same cache, because it can't >> > write to the root owned cache so it creates a temporary cache owned by your >> > user. >> Oh. My. God. It makes complete sense, but is also completely >> ridiculous. What a bad user experience. > > It seems like it would be completely reasonable for DNF to use the root > cache if it's considered "fresh" by the current configuration. And > actually, possibly even if it's not with a warning that the data might > be out of date, with a flag required if you really want to download the > metadata as a regular user. I don't know what things the unprivileged user can do other than search and info. But off hand I'd say an unprivileged user should not be able to download metadata. Use one /var/cache/dnf always. And if it's stale, just inform the user. Only update the cache if the command is issued by root. Multiple user machines, would each cause separately downloaded copies into /var/tmp/dnf as well? And then, dnf make cache timer is only keeping the /var/cache/dnf copy up to date. So the user copy is always going stale anyway. It's just... I don't see how this is worth it even with a fast internet connection. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
