r49429 - in /trunk/libtest-perltidy-perl/debian: changelog control libtest-perltidy-perl.docs

[jawnsy-guest at users.alioth.debian.org]

Author: jawnsy-guest
Date: Sat Dec 26 15:12:42 2009
New Revision: 49429

URL: http://svn.debian.org/wsvn/pkg-perl/?sc=1&rev=49429
Log:
tidy up for release

Removed:
    trunk/libtest-perltidy-perl/debian/libtest-perltidy-perl.docs
Modified:
    trunk/libtest-perltidy-perl/debian/changelog
    trunk/libtest-perltidy-perl/debian/control

Modified: trunk/libtest-perltidy-perl/debian/changelog
URL: http://svn.debian.org/wsvn/pkg-perl/trunk/libtest-perltidy-perl/debian/changelog?rev=49429&op=diff
==============================================================================
--- trunk/libtest-perltidy-perl/debian/changelog (original)
+++ trunk/libtest-perltidy-perl/debian/changelog Sat Dec 26 15:12:42 2009
@@ -1,15 +1,5 @@
 libtest-perltidy-perl (20070911-1) UNRELEASED; urgency=low
 
-  [ Jonathan Yu ]
   * Initial Release.
 
-  [ Ryan Niebur ]
-  * Update jawnsy's email address
-
-  [ gregor herrmann ]
-  * debian/control: Changed: Replace versioned (build-)dependency on
-    perl (>= 5.6.0-{12,16}) with an unversioned dependency on perl (as
-    permitted by Debian Policy 3.8.3); (build-)depend on perl instead of
-    perl-modules.
-
  -- Ryan Niebur <ryanryan52 at gmail.com>  Tue, 01 Sep 2009 21:19:49 -0700

Modified: trunk/libtest-perltidy-perl/debian/control
URL: http://svn.debian.org/wsvn/pkg-perl/trunk/libtest-perltidy-perl/debian/control?rev=49429&op=diff
==============================================================================
--- trunk/libtest-perltidy-perl/debian/control (original)
+++ trunk/libtest-perltidy-perl/debian/control Sat Dec 26 15:12:42 2009
@@ -2,40 +2,25 @@
 Section: perl
 Priority: optional
 Build-Depends: debhelper (>= 7)
-Build-Depends-Indep: perl, libtext-diff-perl,
-  perltidy (>= 20031021), libfile-finder-perl, libfile-slurp-perl
+Build-Depends-Indep: perl, libtext-diff-perl, perltidy (>= 20031021),
+ libfile-finder-perl, libfile-slurp-perl
 Maintainer: Debian Perl Group <pkg-perl-maintainers at lists.alioth.debian.org>
 Uploaders: Jonathan Yu <jawnsy at cpan.org>
-Standards-Version: 3.8.2
+Standards-Version: 3.8.3
 Homepage: http://search.cpan.org/dist/Test-PerlTidy/
 Vcs-Svn: svn://svn.debian.org/pkg-perl/trunk/libtest-perltidy-perl/
 Vcs-Browser: http://svn.debian.org/viewsvn/pkg-perl/trunk/libtest-perltidy-perl/
 
 Package: libtest-perltidy-perl
 Architecture: all
-Depends: ${perl:Depends}, ${misc:Depends}, libtext-diff-perl,
-  perltidy (>= 20031021), libfile-finder-perl, libfile-slurp-perl
-Description: check that all your files are tidy.
- This rather unflattering comment was made in a piece by Ken Arnold:
+Depends: ${perl:Depends}, ${misc:Depends}, perltidy (>= 20031021),
+ libtext-diff-perl, libfile-finder-perl, libfile-slurp-perl
+Description: module to check formatting of Perl code
+ Test::PerlTidy is a Perl module that checks that the formatting of Perl code
+ is produced using the perltidy program. There are some reasons it might be
+ useful to do this:
  .
- "Perl is a vast swamp of lexical and syntactic swill and nobody
- .
- knows how to format even their own code well, but it's the only
- .
- major language I can think of (with the possible exception of the
- .
- recent, yet very Java-like C#) that doesn't have at least one
- .
- style that's good enough."
- .
- http://www.artima.com/weblogs/viewpost.jsp?thread=74230
- .
- Hmmm... He is sort of right in a way. Then again the piece he wrote was
- related to Python which is somewhat strict about formatting itself.
- .
- Fear not though - now you too can have your very own formatting gestapo in
- the form of Test::PerlTidy! Simply add a test file as suggested above and any
- file ending in .pl, .pm, .t or .PL will cause a test fail unless it is
- exactly as perltidy would like it to be.
- .
- This description was automagically extracted from the module by dh-make-perl.
+  1. If style is mandated in tests, then developers will adhere to it.
+  2. If perltidy decides what is good style, then there is no quibbling.
+  3. Version control will not catch formatting changes.
+  4. Code readability may improve as a result.