The following commit has been merged in the master branch:
commit b3a76130a9af6e68d03c6d9e7c5b0c6ac8bf0615
Author: Raphaël Hertzog <[email protected]>
Date:   Sun Sep 20 12:28:30 2009 +0200

    dpkg-genchanges, Dpkg::Vendor::Default: drop hook before-changes-creation
    
    This hook is useless now that the Ubuntu vendor object uses
    post-process-changelog-entry to add their Launchpad-Bugs-Fixed
    field.

diff --git a/scripts/Dpkg/Vendor/Default.pm b/scripts/Dpkg/Vendor/Default.pm
index 72b9af6..2431738 100644
--- a/scripts/Dpkg/Vendor/Default.pm
+++ b/scripts/Dpkg/Vendor/Default.pm
@@ -72,12 +72,6 @@ supported hooks are:
 The first parameter is a Dpkg::Source::Package object. The hook is called
 just before the execution of $srcpkg->build().
 
-=item before-changes-creation ($fields)
-
-The hook is called just before the content of .changes file is output
-by dpkg-genchanges. The first parameter is a Dpkg::Control object
-representing all the fields that are going to be output.
-
 =item keyrings ()
 
 The hook is called when dpkg-source is checking a signature on a source
@@ -110,8 +104,6 @@ sub run_hook {
 
     if ($hook eq "before-source-build") {
         my $srcpkg = shift @params;
-    } elsif ($hook eq "before-changes-creation") {
-        my $fields = shift @params;
     } elsif ($hook eq "keyrings") {
         return ();
     } elsif ($hook eq "register-custom-fields") {
diff --git a/scripts/dpkg-genchanges.pl b/scripts/dpkg-genchanges.pl
index 1761f18..b13ce23 100755
--- a/scripts/dpkg-genchanges.pl
+++ b/scripts/dpkg-genchanges.pl
@@ -19,7 +19,6 @@ use Dpkg::Substvars;
 use Dpkg::Vars;
 use Dpkg::Changelog qw(parse_changelog);
 use Dpkg::Version qw(parseversion compare_versions);
-use Dpkg::Vendor qw(run_vendor_hook);
 
 textdomain("dpkg-dev");
 
@@ -524,6 +523,5 @@ for my $f (keys %remove) {
     delete $fields->{$f};
 }
 
-run_vendor_hook('before-changes-creation', $fields);
 $fields->output(\*STDOUT); # Note: no substitution of variables
 

-- 
dpkg's main repository


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to