[Pkg-puppet-devel] Packaging puppet modules?

[Thomas Bechtold]

Hi Stig,

On 08/24/2013 09:22 AM, Stig Sandbeck Mathisen wrote:
> Thomas Bechtold <thomasbechtold at jpberlin.de> writes:
> 
>> If we package more than one of "something" we could use the
>> update-alternatives stuff or just put a "Conflicts" in the binary
>> packages.
> 
> The Puppet Master provides environments, where one can use different
> versions of modules at the same time. I do this on several
> puppetmasters.
> 
> If we package one module as a directory in /usr/share/puppet/modules,
> and we want to package module number two, module number one would need
> to be changed.
> 
> There is currently just one "stdlib". There are, on the other hand, 7
> modules providing "mysql", and 8 providing "apt". :)
> 
> Would it make sense to install the module "puppetlabs-apt" to
> /usr/share/puppet/modules.available/puppetlabs-apt, and install a
> symlink "/usr/share/puppet/modules/apt" pointing there, using the
> alternatives system? 

You are right. That make sense. The installed link with
update-alternative should be named puppet-module-apt (in this case) then.

FYI: I wrote a python script to semi-automate the package creation from
a upstream tar.gz tarball. See https://github.com/toabctl/puppetmodule2deb

It's not perfect but a good start for packaging. The script already uses
the update-alternative system. See the README for more information.

Cheers,

Tom


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20130824/adbd108f/attachment.sig>