You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: REFERENCE.rst
+18-90Lines changed: 18 additions & 90 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,13 +41,8 @@ attrib
41
41
42
42
::
43
43
44
-
--inventory PATH Path to an inventory file.
45
-
--mapping Use for mapping between the input keys and the ABOUT field.
46
-
names - mapping.config
47
-
--mapping-file Use a custom mapping file with mapping between input
48
-
keys and ABOUT field names.
49
44
--template PATH Path to a custom attribution template.
50
-
--vartext TEXT Variable texts to the attribution template
45
+
--vartext <key>=<value>Variable text as key=value for use in a custom attribution template.
51
46
--verbose Show all the errors and warning.
52
47
-q, --quiet Do not print any error/warning.
53
48
-h, --help Show this message and exit.
@@ -63,7 +58,6 @@ Assume the following:
63
58
64
59
'/home/about_files/'** contains all the ABOUT files [LOCATION]
65
60
'/home/attribution/attribution.html' is the user's output path [OUTPUT]
66
-
'/home/project/component_list.csv' is the inventory that user want to be generated
67
61
68
62
::
69
63
@@ -74,24 +68,6 @@ Options
74
68
75
69
::
76
70
77
-
--inventory
78
-
79
-
This option allows you to define which ABOUT files should be used for attribution generation.
80
-
For instance,
81
-
'/home/project/component_list.csv' is the inventory that user want to be generated
82
-
83
-
$ about attrib --inventory /home/project/component_list.csv LOCATION OUTPUT
84
-
85
-
--mapping
86
-
87
-
See mapping.config for details
88
-
89
-
--mapping-file
90
-
91
-
Same behavior as `--mapping` but with custom mapping file
92
-
93
-
$ about attrib --mapping-file CUSTOM_MAPPING_FILE_PATH LOCATION OUTPUT
94
-
95
71
--template
96
72
97
73
This option allows you to use your own template for attribution generation.
@@ -175,11 +151,10 @@ gen
175
151
176
152
::
177
153
178
-
--fetch-license KEY Fetch licenses text from a DejaCode API. and
179
-
create <license>.LICENSE side-by-side
180
-
with the generated .ABOUT file using data
181
-
fetched from a DejaCode License Library. The
182
-
following additional options are required:
154
+
--fetch-license api_url api_key Fetch licenses data from DejaCode License
155
+
Library and create <license>.LICENSE
156
+
side-by-side with the generated .ABOUT file.
157
+
The following additional options are required:
183
158
184
159
api_url - URL to the DejaCode License Library
185
160
API endpoint
@@ -188,12 +163,8 @@ gen
188
163
Example syntax:
189
164
190
165
about gen --fetch-license 'api_url' 'api_key'
191
-
--license-notice-text-location PATH Copy the 'license_file' from the directory to
192
-
the generated location.
193
-
--mapping Use for mapping between the input keys and
194
-
the ABOUT field names - mapping.config
195
-
--mapping-file Use a custom mapping file with mapping between input
196
-
keys and ABOUT field names.
166
+
--reference PATH Path to a directory with reference license
167
+
data and text files.
197
168
--verbose Show all the errors and warning.
198
169
-q, --quiet Do not print any error/warning.
199
170
-h, --help Show this message and exit.
@@ -210,39 +181,29 @@ Options
210
181
--fetch-license
211
182
212
183
Fetch licenses text from a DejaCode API. and create <license>.LICENSE side-by-side
213
-
with the generated .ABOUT file using data fetched from a DejaCode License Library.
184
+
with the generated .ABOUT file using data fetched from the DejaCode License Library.
214
185
215
186
This option requires 2 parameters:
216
-
api_url - URL to the DJE License Library
187
+
api_url - URL to the DJE License Library.
217
188
api_key - Hash key to authenticate yourself in the API.
218
189
219
190
In addition, the input needs to have the 'license_expression' field.
220
-
(Please contact nexB to get the api_* value to use for this feature)
191
+
(Please contact nexB to get the api_* value for this feature)
221
192
222
193
$ about gen --fetch-license 'api_url' 'api_key' LOCATION OUTPUT
223
194
224
-
--license-notice-text-location
195
+
--reference
225
196
226
-
Copy the license files and notice files to the generated location based on the
227
-
'license_file' and 'notice_file' value in the input from the directory
197
+
Copy the reference files such as 'license_files' and 'notice_files' to the
198
+
generated location from the specified directory.
228
199
229
200
For instance,
230
-
the directory, /home/licenses_notices/, contains all the licenses and notices that you want:
231
-
/home/license/apache2.LICENSE
232
-
/home/license/jquery.js.NOTICE
201
+
the specified directory, /home/licenses_notices/, contains all the licenses and notices:
202
+
/home/licenses_notices/apache2.LICENSE
203
+
/home/licenses_notices/jquery.js.NOTICE
233
204
234
205
$ about gen --license-notice-text-location /home/licenses_notices/ LOCATION OUTPUT
235
206
236
-
--mapping
237
-
238
-
See mapping.config for details
239
-
240
-
--mapping-file
241
-
242
-
Same behavior as `--mapping` but with custom mapping file
243
-
244
-
$ about attrib --mapping-file CUSTOM_MAPPING_FILE_PATH LOCATION OUTPUT
245
-
246
207
--verbose
247
208
248
209
This option tells the tool to show all errors found.
@@ -265,13 +226,7 @@ inventory
265
226
266
227
::
267
228
268
-
--filter TEXT Filter for the output inventory.
269
229
-f, --format [json|csv] Set OUTPUT file format. [default: csv]
270
-
--mapping Use file mapping.config to collect the defined not supported fields in ABOUT files.
271
-
--mapping-file Use a custom mapping file with mapping between input
272
-
keys and ABOUT field names.
273
-
--mapping-output FILE Use a custom mapping file with mapping between
274
-
ABOUT field names and output keys
275
230
--verbose Show all the errors and warning.
276
231
-q, --quiet Do not print any error/warning.
277
232
-h, --help Show this message and exit.
@@ -285,12 +240,6 @@ Options
285
240
286
241
::
287
242
288
-
-filter TEXT
289
-
290
-
Filter for the output inventory.
291
-
292
-
$ about inventory --filter "license_expression=gpl-2.0" LOCATION OUTPUT
293
-
294
243
The above command will only inventory the ABOUT files which have the "license_expression: gpl-2.0"
295
244
296
245
-f, --format [json|csv]
@@ -299,28 +248,6 @@ Options
299
248
300
249
$ about inventory -f json LOCATION OUTPUT
301
250
302
-
--mapping
303
-
304
-
See mapping.config for details
305
-
306
-
--mapping-file
307
-
308
-
Same behavior as `--mapping` but with custom mapping file
309
-
310
-
$ about inventory --mapping-file CUSTOM_MAPPING_FILE_PATH LOCATION OUTPUT
311
-
312
-
--mapping-output
313
-
314
-
Same behavior as `--mapping-file` but with custom mapping file
315
-
In the custom mapping file, the left side is the custom key name where
316
-
the right side is the ABOUT field name. For instance,
317
-
Component: name
318
-
319
-
The "Component" is a custom field name for the output
320
-
The "name" is one of the defaul ABOUT field name that user want to convert
321
-
322
-
$ about inventory --mapping-output CUSTOM_MAPPING_FILE_PATH LOCATION OUTPUT
323
-
324
251
--verbose
325
252
326
253
This option tells the tool to show all errors found.
@@ -408,4 +335,5 @@ Options
408
335
409
336
Special Notes
410
337
=============
411
-
When using the `column_filters` configuration, all the standard required columns (`about_resource` and `name`) and the user definied `required_columns` need to be included.
338
+
When using the `column_filters` configuration, all the standard required columns
339
+
(`about_resource` and `name`) and the user defined `required_columns` need to be included.
0 commit comments