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
* '+' and '(' and ')' is now supported in license_expression
212
229
* The key 'about_resource_path' is removed
213
230
* Revert back the requirement of the 'name' field
@@ -242,7 +259,8 @@ Changelog
242
259
243
260
* New `--vartext` option for `attrib`
244
261
* Add support for `checksum_sha256` and `author_file`
245
-
* `check` command will not count INFO message as error when `--verbose` is set
262
+
* `check` command will not count INFO message as error when `--verbose`
263
+
is set
246
264
* Update `track_change` to `track_changes`
247
265
* New `--filter` and `--mapping-output` options for `inventory`
248
266
@@ -262,7 +280,8 @@ Changelog
262
280
Release 3.1.0
263
281
264
282
* Fixed JSON input from AboutCode manger export and ScanCode output
265
-
* Added a new option `mapping-file` to support using a custom file for mapping
283
+
* Added a new option `mapping-file` to support using a custom file for
284
+
mapping
266
285
* Change the name of the option `--show-all` to `--verbose`
267
286
* Better error handling for copying file with permission issue
268
287
* Support timestamp in attribution output
@@ -274,28 +293,27 @@ Changelog
274
293
275
294
Release 3.0.*
276
295
277
-
ABOUT files is now YAML formatted.
278
-
Supported license expression.
279
-
Supported JSON input and output format: https://github.com/nexB/aboutcode-toolkit/issues/246 and https://github.com/nexB/aboutcode-toolkit/issues/277
280
-
Support Python 3: https://github.com/nexB/aboutcode-toolkit/issues/280
281
-
Refined help texts
282
-
Refined USAGE texts
283
-
Refined SPECs
296
+
ABOUT files is now YAML formatted. Supported license expression.
297
+
Supported JSON input and output format:
298
+
https://github.com/nexB/aboutcode-toolkit/issues/246 and
299
+
https://github.com/nexB/aboutcode-toolkit/issues/277 Support Python 3:
300
+
https://github.com/nexB/aboutcode-toolkit/issues/280 Refined help texts
301
+
Refined USAGE texts Refined SPECs
284
302
285
303
Input key changes:
286
-
==================
287
-
`about_file` is replaced by `about_file_path`
288
-
`dje_license_key` is replaced by `license_expression`
289
-
`version` is no longer a required field
290
-
`home_url` is now `homepage_url`
304
+
305
+
`about_file` is replaced by `about_file_path` `dje_license_key` is
306
+
replaced by `license_expression` `version` is no longer a required
307
+
field `home_url` is now `homepage_url`
291
308
292
309
API Updated:
293
-
============
294
-
- Break down the 3 major functions: `inventory`, `genabout` and `genattrib` into 3 subcommands:
295
-
i.e.
296
-
`about inventory`, `about generate` and `about attrib`
297
310
298
-
- A new `check` subcommand: https://github.com/nexB/aboutcode-toolkit/issues/281
311
+
- Break down the 3 major functions: `inventory`, `genabout` and
312
+
`genattrib` into 3 subcommands:
313
+
i.e. `about inventory`, `about generate` and `about attrib`
Copy file name to clipboardExpand all lines: docs/source/general.rst
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -219,7 +219,7 @@ The attributes that can be set in a configuration file are:
219
219
- field_renamings: An optional map of source field name to target new field
220
220
name that is used to rename CSV/JSON/XLSX fields.
221
221
222
-
.. code-block::none
222
+
.. code-block::
223
223
224
224
field_renamings:
225
225
about_resource : 'Directory/Location'
@@ -238,7 +238,7 @@ renamed to "about_resource" and "foo" to "bar":
238
238
For instance with this configuration, an error will be reported if the fields "name"
239
239
and "version" are missing, or if any entry does not have a value set for these fields:
240
240
241
-
.. code-block::none
241
+
.. code-block::
242
242
243
243
required_fields:
244
244
- name
@@ -252,7 +252,7 @@ and "version" are missing, or if any entry does not have a value set for these f
252
252
For instance with this configuration, the target file will only contains the "name" and
253
253
"version" fields:
254
254
255
-
.. code-block::none
255
+
.. code-block::
256
256
257
257
field_filters:
258
258
- name
@@ -265,7 +265,7 @@ For instance with this configuration, the target file will only contains the "na
265
265
266
266
For instance with this configuration, the target file will not contain the "type" and "temp" fields:
267
267
268
-
.. code-block::none
268
+
.. code-block::
269
269
270
270
exclude_fields:
271
271
- type
@@ -280,7 +280,7 @@ are defined here: :ref:`reference`
280
280
281
281
Here is an example of a gen command:
282
282
283
-
.. code-block::none
283
+
.. code-block::
284
284
285
285
about gen --fetch-license --reference /Users/harrypotter/myLicenseNoticeFiles/ /Users/harrypotter/myAboutFiles/myProject-bom.csv /Users/harrypotter/myAboutFiles/
286
286
@@ -299,7 +299,7 @@ This gen example command does the following:
299
299
Review the generated ABOUT file(s) to determine if it meets your requirements. Here is a
300
300
simple example of a linux-redhat-7.2.ABOUT file that documents the directory /linux-redhat-7.2/ :
301
301
302
-
.. code-block::none
302
+
.. code-block::
303
303
304
304
about_resource: .
305
305
name: Linux RedHat
@@ -354,7 +354,7 @@ here are a few relatively simple concepts that relate to the attribution documen
354
354
The simplest modifications to the default_html.template file involve the labels and standard
355
355
text. For example, here is the default template text for the Table of Contents:
356
356
357
-
.. code-block::none
357
+
.. code-block::
358
358
359
359
<div class="oss-table-of-contents">
360
360
{% for about_object in abouts %}
@@ -367,7 +367,7 @@ text. For example, here is the default template text for the Table of Contents:
367
367
If you would prefer something other than a simple space between the component name and
368
368
the component version, you can modify it to something like this:
369
369
370
-
.. code-block::none
370
+
.. code-block::
371
371
372
372
<div class="oss-table-of-contents">
373
373
{% for about_object in abouts %}
@@ -392,7 +392,7 @@ following example, which is intended to support a "license reference" rather tha
392
392
document, the customized template modifies the data grouping to use a custom field
393
393
called "confirmed_license":
394
394
395
-
.. code-block::none
395
+
.. code-block::
396
396
397
397
<div class="oss-table-of-contents">
398
398
{% for group in abouts | groupby('confirmed_license') %}
@@ -410,7 +410,7 @@ using the jinja2 for-loop capabilities. Notice that the variable "group.grouper.
410
410
actually the license name here, and that “License URL” can be any URL that you have chosen
411
411
to store in your .ABOUT files:
412
412
413
-
.. code-block::none
413
+
.. code-block::
414
414
415
415
{% for group in abouts | groupby('confirmed_license') %}
416
416
{% for confirmed_license in group.grouper.value %}
0 commit comments