Forum: CFEngine Help Subject: how does package list caching work? Author: nickanderson Link to topic: https://cfengine.com/forum/read.php?3,25629,25629#msg-25629
I am curious how this works. It seems that a packages install status is cached. That cache appears to be updated when package_list_update_command runs and package_list_update_command execution frequency is governed by package_list_update_ifelapsed. There doesn't seem to be any seperate notion of update available packages where you might query an upstream repository to see whats new. Those operations seem seperate to me. If a package is uninstalled I dont think I need to wait for the package manager to refresh its packages from upstream in order to notice that a package was removed. Perhaps there should be a seperate body template directive to manage that. Or maybe the copbl should use non network based refresh package list updating and expect end users to have a seperate promise at some interval to refresh the available packages from the repository. Maybe im jut out in left field though. thoughts? _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
