You can, but it would be nice not not have to do that for one or two packages. My hack has been to set a ‘creates’ on a file that the package installs. That doesn’t help for versioning, but it avoid repetitive installs.
David
yum can still take filesystem paths though.
Regarding Cisco, I found that Puppet already has this functionality:
https://puppetlabs.com/blog/puppet-network-device-management/
Edgars
Cisco hardware is generally difficult because it comes in difficult flavors (Catalyst, Nexus, etc) and doesn’t have a lot of strong APIs.
These modules don’t seem to be well received:
http://www.scottyob.com/2012/12/08/my-experiences-of-managing-a-cisco-switch-with-puppet/
That all being said, I’d like to not discuss other CM tools too much on this list, as a professional courtesy.