| Summary: | Improve license manifest description | ||
|---|---|---|---|
| Product: | [Documentation] Development Manual | Reporter: | Paul Eggleton <bluelightning> |
| Component: | development | Assignee: | Simone Weiß <simone.p.weiss> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, elizabeth.flanagan, idadelm, paul, randy.macleod, ross.burton, sgw, simone.p.weiss, tracy.graydon, vineela.tummalapalli |
| Version: | 1.8 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Paul Eggleton
2015-03-18 10:11:15 UTC
Tracy... Once I have this information I can get it into the dev-manual. Thanks, Scott This bug is five years old - where can I get current information concerning the open source files and packages? Does the archiver class not fit this requirement? See https://www.yoctoproject.org/docs/3.1/mega-manual/mega-manual.html#maintaining-open-source-license-compliance-during-your-products-lifecycle Vineela, Can you answer Mark's question? Paul do you have any tips for Mark? The content in Mega manual to me looks good. Paul can you please provide the required inputs. Looking for someone to work on this bug. Will love to work on this bug. (In reply to comment #6) > Looking for someone to work on this bug. Will love to. Turns out the relevant section of the documentation does need an update. Specifically it's been expanded a lot since this bug was filed, but now recommends using meta-spdxscanner instead of the integrated SPDX class. https://docs.yoctoproject.org/dev-manual/common-tasks.html#providing-spdx-files (In reply to Ross Burton from comment #9) > Turns out the relevant section of the documentation does need an update. > Specifically it's been expanded a lot since this bug was filed, but now > recommends using meta-spdxscanner instead of the integrated SPDX class. > > https://docs.yoctoproject.org/dev-manual/common-tasks.html#providing-spdx- > files Checked the current state of the documentation. https://docs.yoctoproject.org/dev/dev-manual/sbom.html#creating-a-software-bill-of-materials already recommends to use SPDX class. I would consider the Bug as obsolete/fixed already. Ross if you agree, I would suggest closing this bug, else a hint what is missing would be appreciated. OK checked docu vs create-spdx.bbclass. It is potrayed in the manual that just inheriting create-spdx in the conf will produce a spdx.json in ´ tmp/deploy/images/MACHINE/. That is not where I found the json on trying, it was in tmp/deploy/spdx/MACHINE not in images. At least that I will update for the documentation. Checked again with clean workspace, will just add notes for the new talk and reformat the options to make them more clear. bulk change to add Saul's non-WR address. Bulk change: Remove Saul's old WR address. |