Thank you for the valuable infos, I agree that differences are enough to require a dedicated solaris subclass, to keep changes isolated and don't fiddle with existing classes linux oriented. The approach: "Custom packages using pkgadd, Solaris OS packages using pkgutil, OpenCSW using pkgutil." seems sane to me and flexible enough to manage exotic packages.
Are your modules, Aareon, published somewhere? I've learnt a lot about Solaris (and its madness :-) just seeing Deet's ones... Ciao al -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4hox7_nnfhUJ. To post to this group, send email to puppet-users@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.
