On 12/17/15 12:13 PM, pagure@pagure.io wrote:
ausil opened a new pull-request against the project: koji that you are following: Enable keepcache in koji dnf conf
koji
Enable keepcache in koji dnf conf
What's the cache expiration policy? Is there a size limit? I'm concerned that this could cause builder disks to fill up with cached packages.
this is a cache that is only inside of the chroot it is gone after the buildroot is cleaned up. All this change does is make dnf behave the same as yum.
Earlier request here: https://lists.fedorahosted.org/archives/list/koji-devel%40lists.fedorahosted.org/thread/ZIBY53JAURLT3QRBBJIJJ7EZWLZDE3TI/
In essence, yum defaults to keepcache=1, dnf defaults to keepcache=0, so this is just getting dnf to behave the way we're used to.
Granted, the use case that motivates the bug seems like a terrible, terrible hack.
The use case (getting the original %config files) was discussed on Fedora devel recently: https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/message/TKJB5SDTGMXVRV2DJ7XWK7ZKGX3HXMFN/
@mikem ping
rebased and pulled in
Pull-Request has been closed by mikem