Hi all, as it appears to be my first post here - Hi GROUP! I''m quite experienced user of cfengine2 trying out pupped in some dev environment. So, now setting full controlled CentOS5 installation. Have two rpm''s which require each others files to be present in the system. 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? thanks, adam -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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. cYa, Avi -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
2009/11/26 Avi Miller <avi.miller@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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
2009/11/27 Paul Nasrat <pnasrat@googlemail.com>> 2009/11/26 Avi Miller <avi.miller@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 > >Hi, thanks both of you for the answers. I think will try with the local yum repo approach. Sounds good to me. One package contains libs and one executables. Executable indeed require the libs package which is pretty logical but the libs packages has the runtime in the dependenciens too (here''s the problem). Those are not my own packages. I do have the SRPM so I could try to fix the deps and rebuld although it sounds like much more work than creating the repo. Thanks again and looking forward to have my puppet setup completed hopefully today [; adam -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.