On Wed, Dec 22, 2010 at 09:55:27AM -0800, Luke Kanies wrote: > It's a bit more complicated for packages, because the dependency trees are so > large, but is it possible to pull the dependency graph of these services? > > IMO, that's the "right" long-term direction: importing external dependency > graphs so we don't have this kind of problem. Anything else is essentially > hacking around the actual problem. In terms of hacking around the problem, > the best answer that I can see is something like the clean/dirty bits. Yes, > you can still break it, but it's the best we can get.
Just had another thought. If someone specifies
# Assume that openssh and /etc/init.d/sshd are absent and I'd apply
package { 'openssh': ensure => installed }
service { 'sshd': ensure => running, require => Package['openssh']}
Prefetching services would make no sense here, because the service ssh
would just be absent. And after the package is installed it might run.
So even resources of another type can influence my service resource.
Arg. Seems like prefetching isnt such a brilliant idea after all...
Maybe it's just useful where it is used right now: In the parsedfile
provider.
-Stefan
pgp4ylZjC8x3F.pgp
Description: PGP signature
