[Pkg-puppet-devel] puppetlabs-inifile ready

Thomas Bechtold thomasbechtold at jpberlin.de
Mon Sep 2 05:51:33 UTC 2013

On 09/01/2013 11:12 PM, Stig Sandbeck Mathisen wrote:
> To add a tarball to the pristine-tar branch, you can do the following:
> $ uscan --download-current-version --verbose
> $ pristine-tar commit ../puppet-module-puppetlabs-inifile_1.0.0.orig.tar.gz
> $ git push origin pristine-tar
>> Except the pristine-tar thing, I guess the package is ready for
>> review and upload.
> Good.  I'll upload it.  I have a few comments for later packaging and
> updates.


> You may want to add a section for the packaging (debian/*) in
> debian/copyright, with a license for the packaging.  I usually use the
> same license as the upstream work.  Not sure how strict the FTP-master
> are about that.  I guess we'll find out. :)

I'll add that to stdlib, inifile and other packages.

> Also, should we add a standardised
> /usr/share/doc/${package}/README.Debian?
> It could say something like:
>  This package contains a module for use by puppet.  It is
>  automatically added to the module load path of puppet's default
>  environment, and should be ready for use.
>  You can use "update-alternatives --config puppet-module-<modulename>"
>  to configure which module should appear in the module path of the
>  default puppet environment, in case multiple modules which provide
>  the same name are installed.

+1 . I can add that, too.

btw. I'm subscribed to the list.



-------------- 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/20130902/19ccc297/attachment.sig>

More information about the Pkg-puppet-devel mailing list