1Dpkg::Vendor::Default(3) libdpkg-perl Dpkg::Vendor::Default(3)
2
6 Dpkg::Vendor::Default - default vendor object
7
9 A vendor object is used to provide vendor specific behaviour in various
10 places. This is the default object used in case there's none for the
11 current vendor or in case the vendor could not be identified (see
12 Dpkg::Vendor documentation).
13 It provides some hooks that are called by various dpkg-* tools. If you
15 need a new hook, please file a bug against dpkg-dev and explain your
16 need. Note that the hook API has no guarantee to be stable over an
17 extended period of time. If you run an important distribution that
18 makes use of vendor hooks, you'd better submit them for integration so
19 that we avoid breaking your code.
20
22 $vendor_obj = Dpkg::Vendor::Default->new()
23 Creates the default vendor object. Can be inherited by all vendor
24 objects if they don't need any specific initialization at object
25 creation time.
26 $vendor_obj->run_hook($id, @params)
28 Run the corresponding hook. The parameters are hook-specific. The
29 supported hooks are:
30 before-source-build ($srcpkg)
32 The first parameter is a Dpkg::Source::Package object. The
33 hook is called just before the execution of
34 $srcpkg->build().
35 package-keyrings ()
37 The hook is called when dpkg-source is checking a signature
38 on a source package (since dpkg 1.18.11). It takes no
39 parameters, but returns a (possibly empty) list of vendor-
40 specific keyrings.
41 archive-keyrings ()
43 The hook is called when there is a need to check signatures
44 on artifacts from repositories, for example by a download
45 method (since dpkg 1.18.11). It takes no parameters, but
46 returns a (possibly empty) list of vendor-specific
47 keyrings.
48 archive-keyrings-historic ()
50 The hook is called when there is a need to check signatures
51 on artifacts from historic repositories, for example by a
52 download method (since dpkg 1.18.11). It takes no
53 parameters, but returns a (possibly empty) list of vendor-
54 specific keyrings.
55 builtin-build-depends ()
57 The hook is called when dpkg-checkbuilddeps is initializing
58 the source package build dependencies (since dpkg 1.18.2).
59 It takes no parameters, but returns a (possibly empty) list
60 of vendor-specific Build-Depends.
61 builtin-build-conflicts ()
63 The hook is called when dpkg-checkbuilddeps is initializing
64 the source package build conflicts (since dpkg 1.18.2). It
65 takes no parameters, but returns a (possibly empty) list of
66 vendor-specific Build-Conflicts.
67 register-custom-fields ()
69 The hook is called in Dpkg::Control::Fields to register
70 custom fields. You should return a list of arrays. Each
71 array is an operation to perform. The first item is the
72 name of the operation and corresponds to a field_* function
73 provided by Dpkg::Control::Fields. The remaining fields are
74 the parameters that are passed unchanged to the
75 corresponding function.
76 Known operations are "register", "insert_after" and
78 "insert_before".
79 post-process-changelog-entry ($fields)
81 The hook is called in Dpkg::Changelog to post-process a
82 Dpkg::Changelog::Entry after it has been created and filled
83 with the appropriate values.
84 update-buildflags ($flags)
86 The hook is called in Dpkg::BuildFlags to allow the vendor
87 to override the default values set for the various build
88 flags. $flags is a Dpkg::BuildFlags object.
89 builtin-system-build-paths ()
91 The hook is called by dpkg-genbuildinfo to determine if the
92 current path should be recorded in the Build-Path field
93 (since dpkg 1.18.11). It takes no parameters, but returns a
94 (possibly empty) list of root paths considered acceptable.
95 As an example, if the list contains "/build/", a Build-Path
96 field will be created if the current directory is
97 "/build/dpkg-1.18.0". If the list contains "/", the path
98 will always be recorded. If the list is empty, the current
99 path will never be recorded.
100
102 Version 0.xx
103 This is a private module.
1041.18.25 2018-06-17 Dpkg::Vendor::Default(3)