{
    "mode": "perldoc",
    "parameter": "Dpkg::Vendor::Default",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/perldoc/Dpkg%3A%3AVendor%3A%3ADefault/json",
    "generated": "2026-06-13T21:29:19Z",
    "sections": {
        "NAME": {
            "content": "Dpkg::Vendor::Default - default vendor class\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "A vendor class is used to provide vendor specific behaviour in various places. This is the\ndefault class used in case there's none for the current vendor or in case the vendor could not\nbe identified (see Dpkg::Vendor documentation).\n\nIt provides some hooks that are called by various dpkg-* tools. If you need a new hook, please\nfile a bug against dpkg-dev and explain your need. Note that the hook API has no guarantee to be\nstable over an extended period of time. If you run an important distribution that makes use of\nvendor hooks, you'd better submit them for integration so that we avoid breaking your code.\n",
            "subsections": []
        },
        "METHODS": {
            "content": "$vendorobj = Dpkg::Vendor::Default->new()\nCreates the default vendor object. Can be inherited by all vendor objects if they don't need\nany specific initialization at object creation time.\n\n$vendorobj->runhook($id, @params)\nRun the corresponding hook. The parameters are hook-specific. The supported hooks are:\n\nbefore-source-build ($srcpkg)\nThe first parameter is a Dpkg::Source::Package object. The hook is called just\nbefore the execution of $srcpkg->build().\n\npackage-keyrings ()\nThe hook is called when dpkg-source is checking a signature on a source package\n(since dpkg 1.18.11). It takes no parameters, but returns a (possibly empty) list of\nvendor-specific keyrings.\n\narchive-keyrings ()\nThe hook is called when there is a need to check signatures on artifacts from\nrepositories, for example by a download method (since dpkg 1.18.11). It takes no\nparameters, but returns a (possibly empty) list of vendor-specific keyrings.\n\narchive-keyrings-historic ()\nThe hook is called when there is a need to check signatures on artifacts from\nhistoric repositories, for example by a download method (since dpkg 1.18.11). It\ntakes no parameters, but returns a (possibly empty) list of vendor-specific\nkeyrings.\n\nbuiltin-build-depends ()\nThe hook is called when dpkg-checkbuilddeps is initializing the source package build\ndependencies (since dpkg 1.18.2). It takes no parameters, but returns a (possibly\nempty) list of vendor-specific Build-Depends.\n\nbuiltin-build-conflicts ()\nThe hook is called when dpkg-checkbuilddeps is initializing the source package build\nconflicts (since dpkg 1.18.2). It takes no parameters, but returns a (possibly\nempty) list of vendor-specific Build-Conflicts.\n\nregister-custom-fields ()\nThe hook is called in Dpkg::Control::Fields to register custom fields. You should\nreturn a list of arrays. Each array is an operation to perform. The first item is\nthe name of the operation and corresponds to a field* function provided by\nDpkg::Control::Fields. The remaining fields are the parameters that are passed\nunchanged to the corresponding function.\n\nKnown operations are \"register\", \"insertafter\" and \"insertbefore\".\n\npost-process-changelog-entry ($fields)\nThe hook is called in Dpkg::Changelog to post-process a Dpkg::Changelog::Entry after\nit has been created and filled with the appropriate values.\n\nupdate-buildflags ($flags)\nThe hook is called in Dpkg::BuildFlags to allow the vendor to override the default\nvalues set for the various build flags. $flags is a Dpkg::BuildFlags object.\n\nupdate-buildprofiles ($buildprofilesref)\nThe hook is called in Dpkg::BuildProfiles to allow the vendor to override the\ndefault values set. $buildprofilesref is a array ref to Dpkg::BuildProfiles\nobject.\n\nbuiltin-system-build-paths ()\nThe hook is called by dpkg-genbuildinfo to determine if the current path should be\nrecorded in the Build-Path field (since dpkg 1.18.11). It takes no parameters, but\nreturns a (possibly empty) list of root paths considered acceptable. As an example,\nif the list contains \"/build/\", a Build-Path field will be created if the current\ndirectory is \"/build/dpkg-1.18.0\". If the list contains \"/\", the path will always be\nrecorded. If the list is empty, the current path will never be recorded.\n\nbuild-tainted-by ()\nThe hook is called by dpkg-genbuildinfo to determine if the current system has been\ntainted in some way that could affect the resulting build, which will be recorded in\nthe Build-Tainted-By field (since dpkg 1.19.5). It takes no parameters, but returns\na (possibly empty) list of tainted reason tags (formed by alphanumeric and dash\ncharacters).\n\nsanitize-environment ()\nThe hook is called by dpkg-buildpackage to sanitize its build environment (since\ndpkg 1.20.0).\n",
            "subsections": []
        },
        "CHANGES": {
            "content": "",
            "subsections": [
                {
                    "name": "Version 0.xx",
                    "content": "This is a private module.\n"
                }
            ]
        }
    },
    "summary": "Dpkg::Vendor::Default - default vendor class",
    "flags": [],
    "examples": [],
    "see_also": []
}