You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not as used to Debian as I'm used to RedHat, so take this with a grain of salt: Should we update apt cache before installing the packages? There are similar tasks in out Molecule checks but not in the actual roles.
We should update the cache if we want to install an actual package or update an existed one. Debian does not know about the new available packages without cache update. We can also integrate the cache update in the installation task.
Yes. How about opening an issue or even a project/milestone for updating? And for now we check whether it's installed and if not, we run the cache update? Would that be ok? We need to keep the update in the Molecule configuration because that's for a different set of packages.
I know, checking for the existence of the configuration directory is not
the best way. But it's way faster than quering the package manager every
time.
fixes#167
I'm not as used to Debian as I'm used to RedHat, so take this with a grain of salt: Should we update
apt
cache before installing the packages? There are similar tasks in out Molecule checks but not in the actual roles.In https://github.com/geerlingguy/ansible-role-mysql @geerlingguy has a task that checks whether the package is already installed. And if not, then her refreshes the
apt
cache. Should speed up the process significantly.The text was updated successfully, but these errors were encountered: