[Pkg-puppet-devel] Packaging puppet modules?

[Stig Sandbeck Mathisen]

Thomas Bechtold <thomasbechtold at jpberlin.de> writes:

> Just tried to package the stdlib from puppetlabs and you can find the
> results here:
>
> https://github.com/toabctl/pkg-puppet-module-puppetlabs-stdlib
>
> The package uses git-buildpackage and installes the module into
> /usr/share/puppet/modules/ .

> If you like the idea to package some puppet modules I would be happy
> to move the git repository to pkg-puppet on alioth. I'm only a debian
> maintainer so I would need a sponsor for the package (and for the
> upcoming other puppet modules).

The pkg-puppet repository on alioth would be a good place for the
packaging of puppet modules.

I'd be happy to sponsor the packages.

There is a good possibility of module and dependency collisions. Puppet
module metadata refers to itself and other modules as "user/module",
while the directories used, and the manifests in the modules themselves
drop the "user/" part.

When the module "something" is provided by foo-something and
bar-something, how should the right one be selected? Is registering
"puppet-module-something" in "update-alternatives" useful for this?

There is no guarantee that "foo-something" and "bar-something" actually
does the same "something".

(This is more a problem to be fixed by the upstream, Puppet Labs, but I
would like to mention it here just in case someone has a solution, or a
workaround that can be used in Debian)

-- 
Stig Sandbeck Mathisen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20130818/ae573bbe/attachment.sig>