2010/3/11 micah anderson <[email protected]>: > On Thu, 11 Mar 2010 14:05:50 +0100, martin f krafft <[email protected]> > wrote: >> The idea comes from David Schmitt's common module, which creates >> /var/lib/puppet/modules/common to store stuff the module needs. >> I think it would make sense to create /var/lib/puppet/modules by the >> puppet package so that other modules can just drop their own >> directories in there without each and every one of them having to >> jump through hoops to ensure existence of the parent. > > I think that the modules directory should only be created if Debian was > shipping modules as packages and they were using that directory, or if > debian would use that path in the config as a module path.
++ How far do we take this? Most people start off with plain modules, and end up moving towards modules in environments, and it's just impractical imho to provide an appropriate directory structure in that case. > > if somebody uses modules_dir they should create that dir with puppet, > not with the package, afterall this is what puppet is for. not everyone > on Debian uses this approach, DavidS modules, while useful for people to > get going, are not used by every Debian user. > > For example, here is an alternative approach (one that is IMHO more cleaner): > > http://www.devco.net/archives/2010/02/19/building_files_from_fragments_with_puppet.php > > micah > > _______________________________________________ > Pkg-puppet-devel mailing list > [email protected] > http://lists.alioth.debian.org/mailman/listinfo/pkg-puppet-devel > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
