| Summary: | feature request: manifest files per license | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Frans Meulenbroeks <fransmeulenbroeks> |
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Undecided | CC: | alexandru.c.georgescu, elizabeth.flanagan, jiajun.xu, kergoth, poky.bs.watcher, poky.watcher, richard.purdie, ross.burton, sgw, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Frans Meulenbroeks
2012-05-09 06:13:40 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. Hi, Are there any updates regarding this? Thanks, Alex. 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. Frans, Did what Chris suggest solve your issue? 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. It appears the information has been provided. 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. Setting this to undecided 2.6 so we can discuss in bug triage. 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. |