2009/11/26 Avi Miller <avi.mil...@gmail.com>: > Hi Adam, > > sektoid0 wrote: >> Only chance to cleanly install it is to put both packages at >> once to rpm -i rpm1 rpm2. Or -i --nodeps on each one. It seems that >> non of these options are present in puppet package type. Any ideas? > > Create a local Yum repository for those RPMs (using the createrepo tool > in the yum-utils package) and then use Puppet's Package provider to > install them. Yum will handle the cross-package dependencies.
Indeed using a dep solver rather than the package manager directly is probably the right approach to managing this sort of thing. In general cycles with a dependency graph are bad (in some cases fairly unavoidable glibc/glibc-common), if these are your own packages you are building you might want to think about the design. Is there actually a common shared (filesystem) dir layout requirement that both packages are carrying some of that could be split? Are the deps runtime, install time (for scriptlets) or just you need both installed to start a service? What happens in a single transaction is bascially loop cutting in the ordering - which is why it may 'work' on the combined command line or using yum. However the loop cutting is fairly simple so if you can build your packages to avoid the loop that's good. Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
