3 ms·
Well, you just change state to absent and it will be uninstalled. You don't need two tasks for that. It's one task that describes state of a package. That state
by szszrk 4y ago
Well, you just change state to absent and it will be uninstalled. You don't need two tasks for that. It's one task that describes state of a package. That state can be a number of things. You don't even need to create a task for each package, you can easily make a loop over a predefined key:value list with statuses of packages you want/don't want.
What I mean is that It's not an impossible goal with Ansible. Not even a tough one.
- oddlama 4y agoNeither impossible nor tough, but also not a clean way of managing state. You need to keep track of all past things you once did but no longer need.
- INTPenis 4y agoI guess the point is that it's already there and ready to be used. Not trying to discourage innovation and enthusiasm. I just want my router setup.
- szszrk 4y agoI don't think this is true. What happened to things "you no longer need", did these packages disappear? Or you suddenly trust system defaults? If you do then why with minimalist approach at all. It feels very inconsistent to me. You can always start from a minimalist system image and then add a few packages you need using Ansible. Is that really that different?