Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=524451
--- Comment #3 from Jeroen van Meeuwen <kanarip(a)kanarip.com> 2009-10-11 08:54:05
EDT ---
(In reply to comment #1)
I presume the idea is that the module files shipped in the package
should not
need to be edited? If not, would they be better placed in
/usr/share/puppet/modules/<source>/<module>? (Or
.../modules/<source>/<environment>/<module> if you have different
content to
ship in development, testing, and production versions of the module.)
Then, users could create symlinks in /var/lib/puppet (or where ever) to meet
their own environments layout.
Not a very bad idea. /usr/share/puppet/puppetmanaged.org/development/yum/ could
probably be a better location for these packaged modules, which indeed would
not need to be changed by the user (presumably).
This might well be something to bring up on the puppet-dev or -users
list. I
know the common modules haven't gotten very far yet, but I'm sure other puppet
users have given this problem some thought and it might be beneficial to try
and come up with a somewhat standard layout for shipping module packages.
Plus, then it could be documented on the puppet wiki and potentially save you
some work writing a nice README.Fedora.
The documentation for these type of modules is extensive anyway, since it
covers various use-cases (though not all of them). Obviously documentation is
always a work in progress, but here's a recent version:
http://www.puppetmanaged.org/documentation/Reference_Guide-Modules-Yum_Mo...
I'm not sure getting the people working on Puppet Common Modules on board is
going to make this any more fast or any more sustainable at this point, given
as how Puppet Common Modules has not made any significant progress.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.