On Jan 27, 8:01 am, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: > Hi, > > On 01/27/2012 02:52 PM, Walter Heck wrote: > > > There's something else we need to think about here. Some modules have > > a soft/conditional requirement for other modules. What I mean is that > > if you don't use certain parts of a module, you don't need the module > > that that part of the code refers to. the only decent way I can come > > up with to solve that is to use what for instance in C is done with > > #IFDEF. That way the module could just ignore modules that it doesn't > > _really_ require. > > thanks for pointing this out, but it has been covered (I think) in > another thread already: > > On 01/19/2012 09:17 PM, Nick Fagerlund wrote:
[...] And Nick's approach seems good and useful, but I don't think it addresses Walter's concern. Walter observes that modules' runtime inter-module dependencies can depend on how they are used, and he argues, I think, that that complicates the problem of managing such dependencies via a package management system. For example, if module X depends on module Y only for feature X::ySupport, and I intend never to use X::ySupport, then I might like to avoid installing module Y. If I furthermore want to use module Y2 that is incompatible with module Y, then I might *need* to avoid installing Y. There are ways to handle problems such as those, but it all creates a lot of overhead to make everything work together properly in such a scheme. John A hollow voice says "Plugh". -- 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.
