4 ms·
Chef, puppet, ansible, … Or the redneck version: Have a metapackage in your own repository that uses dependencies/conflicts to pull/remove the packages you wan
by creshal 11y ago
Chef, puppet, ansible, …
Or the redneck version: Have a metapackage in your own repository that uses dependencies/conflicts to pull/remove the packages you want.
- majewsky 11y agoWhat you call "redneck" version is actually how I manage my system configuration. :) The metapackage is the only one that's explicitly installed, ever. (Except for workstations where I might install applications to test them.) Part of system maintenance is to clean out orphaned packages every once in a while, usually as part of the system update.
- creshal 11y ago> What you call "redneck" version is actually how I manage my system configuration. :) Same here. One day I'll get around to migrate everything to Ansible… one day…
- stephenr 11y agoI'm a big fan of this approach too. Combine it with config packages (using something like configure-package-dev from debathena) and you have a very nice little config management system.