On Tue, 24 Jan 2012 10:32:31 +0100 Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote:
> Perhaps there needs to be some kind of "Forge common" module that by > policy can only ever declare virtual resources (packages are a > prominent example). This only takes care of the Forge case. The problem of having the same package being required in multiple places isn't limited to Forge, it's one I run into locally all the time (and I'm sure I'm not the only one). On top of that, once you try to cover multiple distributions where package names diverge, it starts getting hard. And once the packaging itself is different, as in (non-existing) sub-packages... there is no end (1). I don't have the slightest idea as to how all this could be solved in a clean way, but "requiring a common bit of high level code" isn't the global solution I'm myself hoping for. Matthias (1) Example where a nagios plugin requires the package for the nagios perl bindings. It's "nagios-perl" for most RPMs, but not split out and in the main "nagios-plugins" on Gentoo... then for any other plugin from nagios-plugins RPMs, such as "nagios-plugins-file_age", same thing. So you get a big mess with duplicate definitions for the main Gentoo "nagios-plugins" package, or you need yet another layer of high level code hack :-/ -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
