1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
|
#
# This file is part of Config-Model
#
# This software is Copyright (c) 2012 by Dominique Dumont, Krzysztof Tyszecki.
#
# This is free software, licensed under:
#
# The GNU Lesser General Public License, Version 2.1, February 1999
#
[
{
'name' => 'Debian::Dpkg::Control::Source',
'copyright' => [
'2010,2011 Dominique Dumont'
],
'author' => [
'Dominique Dumont'
],
'license' => 'LGPL2',
'element' => [
'Source',
{
'value_type' => 'uniline',
'summary' => 'source package name',
'match' => '\\w[\\w+\\-\\.]{1,}',
'mandatory' => '1',
'type' => 'leaf'
},
'Maintainer',
{
'value_type' => 'uniline',
'summary' => 'package maintainer\'s name and email address',
'mandatory' => '1',
'type' => 'leaf',
'description' => 'The package maintainer\'s name and email address. The name must come first, then the email address inside angle brackets <> (in RFC822 format).
If the maintainer\'s name contains a full stop then the whole field will not work directly as an email address due to a misfeature in the syntax specified in RFC822; a program using this field as an address must check for this and correct the problem if necessary (for example by putting the name in round brackets and moving it to the end, and bringing the email address forward). '
},
'Uploaders',
{
'cargo' => {
'replace_follow' => '!Debian::Dpkg my_config email-updates',
'value_type' => 'uniline',
'type' => 'leaf'
},
'type' => 'list'
},
'Section',
{
'warn_unless' => {
'area' => {
'msg' => 'Bad area. Should be \'non-free\' or \'contrib\'',
'code' => '(not defined) or m!^((contrib|non-free)/)?\\w+$!;'
},
'section' => {
'msg' => 'Bad section.',
'code' => '(not defined) or m!^([-\\w]+/)?(admin|cli-mono|comm|database|devel|debug|doc|editors|education|electronics|embedded|fonts|games|gnome|graphics|gnu-r|gnustep|hamradio|haskell|httpd|interpreters|introspection|java|kde|kernel|libs|libdevel|lisp|localization|mail|math|metapackages|misc|net|news|ocaml|oldlibs|otherosfs|perl|php|python|ruby|science|shells|sound|tex|text|utils|vcs|video|web|x11|xfce|zope)$!;'
},
'empty' => {
'msg' => 'Section is empty',
'code' => 'defined and length'
}
},
'value_type' => 'uniline',
'type' => 'leaf',
'description' => 'The packages in the archive areas main, contrib and non-free are
grouped further into sections to simplify handling.
The archive area and section for each package should be specified in
the package\'s Section control record (see
L<Section 5.6.5|http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Section>).
However, the maintainer of the Debian archive may override
this selection to ensure the consistency of the Debian
distribution. The Section field should be of the form:
'.'=over
'.'=item *
section if the package is in the main archive area,
'.'=item *
area/section if the package is in the contrib or non-free archive areas.
'.'=back
'
},
'Priority',
{
'value_type' => 'enum',
'help' => {
'standard' => 'These packages provide a reasonably small but not too limited character-mode system. This is what will be installed by default if the user doesn\'t select anything else. It doesn\'t include many large applications. ',
'required' => 'Packages which are necessary for the proper functioning of the system (usually, this means that dpkg functionality depends on these packages). Removing a required package may cause your system to become totally broken and you may not even be able to use dpkg to put things back, so only do so if you know what you are doing. Systems with only the required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software. ',
'optional' => '(In a sense everything that isn\'t required is optional, but that\'s not what is meant here.) This is all the software that you might reasonably want to install if you didn\'t know what it was and don\'t have specialized requirements. This is a much larger system and includes the X Window System, a full TeX distribution, and many applications. Note that optional packages should not conflict with each other. ',
'extra' => 'This contains all packages that conflict with others with required, important, standard or optional priorities, or are only likely to be useful if you already know what they are or have specialized requirements (such as packages containing only detached debugging symbols).',
'important' => 'Important programs, including those which one would expect to find on any Unix-like system. If the expectation is that an experienced Unix person who found it missing would say "What on earth is going on, where is foo?", it must be an important package.[5] Other packages without which the system will not run well or be usable must also have priority important. This does not include Emacs, the X Window System, TeX or any other large applications. The important packages are just a bare minimum of commonly-expected and necessary tools.'
},
'type' => 'leaf',
'choice' => [
'required',
'important',
'standard',
'optional',
'extra'
]
},
'Build-Depends',
{
'cargo' => {
'value_type' => 'uniline',
'warn_if_match' => {
'libpng12-dev' => {
'msg' => 'This dependency is deprecated and should be replaced with libpng-dev. See BTS 650601 for details',
'fix' => '$_ = \'libpng-dev\';'
}
},
'class' => 'Config::Model::Debian::Dependency',
'type' => 'leaf'
},
'duplicates' => 'warn',
'type' => 'list'
},
'Build-Depends-Indep',
{
'cargo' => {
'value_type' => 'uniline',
'class' => 'Config::Model::Debian::Dependency',
'type' => 'leaf'
},
'duplicates' => 'warn',
'type' => 'list'
},
'Build-Conflicts',
{
'cargo' => {
'value_type' => 'uniline',
'type' => 'leaf'
},
'type' => 'list'
},
'Standards-Version',
{
'value_type' => 'uniline',
'summary' => 'Debian policy version number this package complies to',
'warn_unless_match' => {
'3\\.9\\.3' => {
'msg' => 'Current standards version is 3.9.3',
'fix' => '$_ = undef; # restore default value'
}
},
'match' => '\\d+\\.\\d+\\.\\d+(\\.\\d+)?',
'default' => '3.9.3',
'type' => 'leaf',
'description' => 'This field indicates the debian policy version number this package complies to'
},
'Vcs-Browser',
{
'compute' => {
'use_eval' => '1',
'formula' => '$maintainer =~ /pkg-perl/ ? "http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/$pkgname.git" : undef ;',
'variables' => {
'maintainer' => '- Maintainer',
'pkgname' => '- Source'
},
'allow_override' => '1'
},
'value_type' => 'uniline',
'summary' => 'web-browsable URL of the VCS repository',
'match' => '^https?://',
'type' => 'leaf',
'description' => 'Value of this field should be a http:// URL pointing to a web-browsable copy of the Version Control System repository used to maintain the given package, if available.
The information is meant to be useful for the final user, willing to browse the latest work done on the package (e.g. when looking for the patch fixing a bug tagged as pending in the bug tracking system). '
},
'Vcs-Arch',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Bzr',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Cvs',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Darcs',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Git',
{
'compute' => {
'use_eval' => '1',
'formula' => '$maintainer =~ /pkg-perl/ ? "git://git.debian.org/pkg-perl/packages/$pkgname.git" : \'\' ;',
'variables' => {
'maintainer' => '- Maintainer',
'pkgname' => '- Source'
},
'allow_override' => '1'
},
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Hg',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Mtn',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'Vcs-Svn',
{
'value_type' => 'uniline',
'summary' => 'URL of the VCS repository',
'type' => 'leaf',
'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface.
The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. '
},
'DM-Upload-Allowed',
{
'value_type' => 'uniline',
'summary' => 'The package may be uploaded by a Debian Maintainer',
'match' => 'yes',
'type' => 'leaf',
'description' => 'If this field is present, then any Debian Maintainers listed in the Maintainer or Uploaders fields may upload the package directly to the Debian archive. For more information see the "Debian Maintainer" page at the Debian Wiki - http://wiki.debian.org/DebianMaintainer'
},
'Homepage',
{
'value_type' => 'uniline',
'type' => 'leaf'
},
'XS-Python-Version',
{
'value_type' => 'uniline',
'status' => 'deprecated',
'experience' => 'advanced',
'type' => 'leaf'
},
'X-Python-Version',
{
'value_type' => 'uniline',
'summary' => 'supported versions of Python ',
'upstream_default' => 'all',
'experience' => 'advanced',
'migrate_from' => {
'use_eval' => '1',
'formula' => 'my $old = $xspython ;
my $new ;
if ($old =~ /,/) {
# list of versions
my @list = sort split /\\s*,\\s*/, $old ;
$new = ">= ". (shift @list) . ", << " . (pop @list) ;
}
elsif ($old =~ /-/) {
my @list = sort grep { $_ ;} split /\\s*-\\s*/, $old ;
$new = ">= ". shift @list ;
$new .= ", << ". pop @list if @list ;
}
else {
$new = $old ;
}
$new ;',
'variables' => {
'xspython' => '- XS-Python-Version'
}
},
'type' => 'leaf',
'description' => 'This field specifies the versions of Python (not versions of Python 3) supported by the source package. When not specified, they default to all currently supported Python (or Python 3) versions. For more detail, See L<python policy|http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions>'
},
'X-Python3-Version',
{
'value_type' => 'uniline',
'summary' => 'supported versions of Python3 ',
'experience' => 'advanced',
'type' => 'leaf',
'description' => 'This field specifies the versions of Python 3 supported by the package. For more detail, See L<python policy|http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions>'
}
]
}
]
;
|
