[Pkg-puppet-devel] Packaging puppet modules?

[Thomas Bechtold]

On 08/18/2013 06:09 PM, Stig Sandbeck Mathisen wrote:
> 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.

Cool! :-)

> 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?

I suggest to keep it simple and as long as we package only one version
of "something" everthing should be fine. If we package more than one of
"something" we could use the update-alternatives stuff or just put a
"Conflicts" in the binary packages.

> 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)

Is there a bug report upstream about this issue?

btw: I requested to join the pkg-puppet team on alioth. As soon as I
have access there, I'll move the packaging stuff from github to alioth.


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/20130819/4a8fd97f/attachment.sig>