also sprach micah anderson <mi...@debian.org> [2010.03.12.2036 +0100]: > The second is dynamically generated file concatentation bits that are > created by a module, and then assembled into a configuration file. These > are typically done in /var/lib/puppet/modules, at least if you are using > this method that DavidS uses. I dont think that this directory should be > created by the package.
Almost: these are typically done in
/var/lib/puppet/modules/$MODULENAME, and since puppet's file type
does not create parent directories, no module can really ever use
/var/lib/puppet/modules/$MODULENAME unless it can rely on
/var/lib/puppet/modules to be there. So unless the admin (or the
Debian package) creates the directory, each module has to jump
through hoops[0] before being able to use the directory, because of
the stupid puppet limitation that an instance cannot be multiply
defined.
Right now, DavidS' common module creates the parent, which means
I'll either have to require the common module, or conflict with it,
but I cannot merely supplement it.
0. e.g. exec { "mkdir --parent /var/lib/puppet/modules" }
--
.''`. martin f. krafft <madd...@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
"most people become bankrupt through having invested too heavily in
the prose of life. to have ruined one's self over poetry is an
honour."
-- oscar wilde
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
