Bug 2442 - feature request: manifest files per license
Summary: feature request: manifest files per license
Status: RESOLVED OBSOLETE
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided enhancement
Target Milestone: 4.99
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-05-09 06:13 UTC by Frans Meulenbroeks
Modified: 2018-03-01 15:44 UTC (History)
10 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frans Meulenbroeks 2012-05-09 06:13:40 UTC 
It would be nice to have a manifest file per license type so users can easily see what packages come under what license.

Alternately there could e.g. be a license.manifest.csv or so that is a csv with all package info on one line (so it can easily be grepped, imported in excel/openoffice/libreoffice, or postprocessed by a script
Comment 1 Jiajun Xu 2012-05-21 08:09:42 UTC 
I would like to mark the feature as "No QA needed", since we are not planning to test license related feature. If there is any requirement for the feature, please tell me.
Comment 2 Alexandru Georgescu 2013-03-14 14:13:02 UTC 
Hi,
Are there any updates regarding this?

Thanks,
Alex.
Comment 3 Christopher Larson 2013-04-29 21:09:53 UTC 
Frans, regarding csv, we're using http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/tree/classes/deploy-license-manifest.bbclass at mentor, it copies the manifest to DEPLOY_DIR_IMAGE at image creation time, and constructs a csv from it next to it there. You might find that useful as an interim solution.
Comment 4 Beth Flanagan 2016-05-11 18:51:26 UTC 
Frans,

Did what Chris suggest solve your issue?
Comment 5 Frans Meulenbroeks 2016-06-07 08:04:41 UTC 
Hi,

What Chris suggested was a workaround; it would probably be nice if there was a standard solution.

Then again, this ticket is 4 years old. I'm not even working for the company that could use this any more, so I have no need for this any more.
Comment 6 Stephen K Jolley 2016-06-13 22:25:22 UTC 
It appears the information has been provided.
Comment 7 Tracy Graydon 2018-02-16 19:34:54 UTC 
 I think is a larger discussion to have around some nice-to-have manifests/artifacts for releases. i.e. Something that captures the commits and branches used for a given release, relevant hashes, and other odds and ends that we use to publish and tag releases. There has been some discussion around this in the past, but it's all been pretty low priority. 

If this is no longer a direct customer need, suggest we close this bug. If we reach a point where we think there is enough value in the work involved in adding some such things, or there is a relevant customer need, we can open new bugs accordingly.
Comment 8 Stephano Cetola 2018-03-01 14:24:30 UTC 
Setting this to undecided 2.6 so we can discuss in bug triage.
Comment 9 Richard Purdie 2018-03-01 15:44:37 UTC 
This has sat for a long time without people knowing what to do with it. I think it needs someone with a specific need and time to work on it which nobody seems to have right now.

Some license handling things are really best done as "post processing". 

If someone has a design for specific work I'd be happy to see a specific feature enhancement and/or patches but for now close this as obsolete as the license handling has changed massively since this was first filed.