Working with dh-make-perl (was: Re: Application naming)
I'll keep my questions together in this thread.
On Mon, May 31, 2010 at 11:19:26PM +0200, gregor herrmann wrote:
> On Mon, 31 May 2010 07:37:37 -1000, Joel Roth wrote:
> > I observe that Padre, another end-user application, has a
> > debian package 'padre', while its optional plugins and
> > libraries are libpadre-*.
> > Naturally I would prefer that naming as well.
> Ack, if it's an app and no module 'nama' sounds more logical.
I'll go with that simpler name, 'nama'.
> [...]at least I vaguely remember discussing
> advantages and disadvantages of both options and of putting it in
> svn/trunk and svn/apps and git :)
Need I be concerned about the
structure of svn repository? Any references to tell me
where and what should I specify regarding svn/trunk or
After running dh-make-perl with
Is this the expected behavior? I'm ready to patch, but would
like to get as much correct as possible by informed use of
Where does dh-make-perl look for short-description and
description? (I see there is a --desc option to dh-make-perl.)
Description: (no short description found)
(no description was found)
This description was automagically extracted from the
module by dh-make-perl.
Where does dh-make-perl look for a license? debian/copyright says:
Copyright: Joel Roth, <firstname.lastname@example.org>
Copyright: 2010, Joel Roth <email@example.com>
License: unparsable or Artistic or GPL-1+