[Pkg-puppet-devel] puppet-module-puppetlabs-stdlib ready for NEW-Queue

Stig Sandbeck Mathisen ssm at debian.org
Sun Sep 1 12:49:48 UTC 2013

Thomas Bechtold <thomasbechtold at jpberlin.de> writes:

> Two more things:
> 1) should the tests/ and spec/ directories be installed in
> /usr/share/puppet/modules.available/puppetlabs-stdlib?

Yes, I think so.

We should at least include "tests/".

If we package "spec/", we also need to package the ".fixtures.yml" in
the module root directory, provide a writable spec/fixtures/ directory,
possibly use some gems we haven't packaged yet. .fixtures.yml may need a
rewrite to use symlinks to dependent modules instead of remote git
repos, etc.

> 2) What about test execution during build?
> We could do something like:
> for F in `ls tests/` ; do puppet apply --modulepath=$PWD/../ --noop
> tests/$F; done
> I'm not sure if this is the correct way but seems that the files in
> tests are intended to be used for smoke testing[1]. But I think the
> tests shouldn't block an upload to the NEW queue.

I agree.

As the subject indicates, should I upload the new package now?

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/20130901/83698e3b/attachment.sig>

More information about the Pkg-puppet-devel mailing list