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
|
=pod
=head1 NAME
slackdtxt - Create package description files for Slackware packages
=head1 SYNOPSIS
B<slackdtxt> B<[>optionsB<]> B<E<lt>tgz file or list of filesE<gt>>
=head1 DESCRIPTION
B<slackdtxt> is tool for creating the package description (packagename.txt)
files that can be see in the Slackware package series directories. It can
also optionally sign the Slackware package with your GnuPG secret key.
All Slackware packages have an 'install/slack-desc' file contained within the
package file. This file gives a brief description of the package and is displayed
by the B<installpkg> program when the package is installed, or by B<upgradepkg>
when the package is upgraded.
Within the Slackware binary distribution package 'series' directories
are the '.t?z' files and an accompanying .txt file. However, the slack-desc files
contained within the .t?z often have comments and 'the handy ruler' which
should B<not> appear the .txt version. B<slackdtxt> removes this and generates
a 'standard' .txt version from the slack-desc file.
B<slackdtxt> can either take an existing B<slack-desc> file and convert it, or
extract the slack-desc from the specified .t?z package file.
The basic purpose of B<slackdtxt> is to build .txt files after you have run
Slackware's official B<SlackBuild> scripts. Slackware's SlackBuild scripts
leave the packages in /tmp, and it is presumed that you would like to move
them into a safe place and create a .txt file at the same time. Therefore slackdtxt
enables you to specify a B<destination directory> in which to copy or move the .t?z
and to create the .txt file.
slackdtxt was written with porting Slackware to other architectures in mind.
=head1 Slackware Package file extensions
Starting with Slackware version 13, four types of package compression formats
are suported.
=over 4
=item B<.tgz> - Gzip
=item B<.tbz> - Bzip2
=item B<.tlz> - LZMA
=item B<.txz> - XZ
=back
Where this document mentions '.t?z', it refers to one of the above formats.
=head1 OPTIONS - GENERAL
=over 4
=item B<-h>, B<--help>
Show the available options and exit
=item B<-v>, B<--version>
Show the version information and exit
=back
=head1 OPTIONS - MAIN
=over 4
=item B<-s>, B<--slackdescfile> <path to slack-desc file>
Specify the name of/path to the 'slack-desc' file.
You would typically want to use this option if you are in the package
build directory that contains the B<slack-desc> file.
B<Note:> You cannot use this option when specifying more than
one .t?z package file; all slack-desc files will be extracted
from the .t?z file.
This option is not mandatory.
=item B<-d>, B<--destdir> <directory>
If this option is specified, slackdtxt will move (or copy, see
B<--nodelete>) the .t?z file into this directory. The .txt and .asc
files will also be created in this directory.
See the examples document for the purpose of this option.
This option is not mandatory.
B<Note:> Omitting this flag implies B<--nodelete>
=item B<-n>, B<--nodelete>
This option is used in conjunction with B<--destdir>
With this option, when slackdtxt has created the .txt file and copied the .t?z file
into the destination directory, it will not delete the original version.
For example, if your file is F</tmp/foobar-2.0-i386-4.tgz>
and you feed slackdtxt B<--destdir> F</data/slackware/> then
the F</tmp/foobar-2.0-i386-4.tgz> will remain.
By default, the original will be deleted B<unless> there is no
destination directory specified by B<--destdir>
=item B<-G>, B<--gpg-sign> <id>
Sign the original .t?z package file with specified GnuPG key. The
GnuPG signature file will have the same name as the .t?z file but with an
extra B<.asc> suffixed (e.g. foobar-1.0-i486-5.tgz.asc).
=back
=head1 EXAMPLES
=over 4
=item # B<slackdtxt> foo-1.00-i486-1.tgz
This will create a single file named foo-1.00-i486-1.txt
within the current working directory. To specify a different
directory, see options B<-d>, B<--destdir>
=item # B<slackdtxt> *.t?z
This will make slackdtxt create '.txt' files for every
'.t?z' package file within the current working directory.
=back
=head1 RETURN VALUES
These are the exit codes that slackdtxt will produce when it encounters
certain problems. You may wish to use these return codes to indicate
success or failure when slackdtxt is called from unattended auto builder
scripts.
=over 4
=item B<0>
Clean exit
slackdtxt exited without encountering any errors.
This is the default exit code.
=item B<1>
Reserved
This error code is not currently used.
=item B<6>
Missing destination directory
The destination directory specified by the B<--destdir> switch does not exist.
=item B<7>
Missing user specified file
A file specified by the user does not exist. Typically this will
be the .t?z package file.
=item B<8>
Error moving data or moved data is corrupt
slackdtxt failed to copy or move a data file correctly, or the file
was moved correctly (B<mv> or B<cp> did not exit with a non-zero value)
but a further verify failed.
=back
=head1 FILES
F</usr/bin/slackdtxt> the slackdtxt script
F</usr/doc/slacktrack-@VERSION@/SLACKDTXT.examples> slackdtxt usage examples
=head1 AUTHOR
Stuart Winter <mozes@slackware.com>
=head1 SEE ALSO
=over 4
B<slacktrack>(8), B<makepkg>(8), B<installpkg>(8), B<explodepkg>(8), B<removepkg>(8), B<pkgtool>(8), B<upgradepkg>(8)
=cut
=back
|
