2442 2012-05-09 06:13:40 +0000 feature request: manifest files per license 2018-03-01 15:44:37 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto unspecified x86 Multiple RESOLVED OBSOLETE Undecided enhancement 4.99 1 fransmeulenbroeks richard.purdie alexandru.c.georgescu elizabeth.flanagan jiajun.xu kergoth poky.bs.watcher poky.watcher richard.purdie ross.burton sgw song.liu --- --- Yes (doc changes required) oldest_to_newest 21240 0 fransmeulenbroeks 2012-05-09 06:13:40 +0000 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 21480 1 jiajun.xu 2012-05-21 08:09:42 +0000 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. 30710 2 alexandru.c.georgescu 2013-03-14 14:13:02 +0000 Hi, Are there any updates regarding this? Thanks, Alex. 32736 3 kergoth 2013-04-29 21:09:53 +0000 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. 62117 4 elizabeth.flanagan 2016-05-11 18:51:26 +0000 Frans, Did what Chris suggest solve your issue? 62692 5 fransmeulenbroeks 2016-06-07 08:04:41 +0000 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. 62945 6 sjolley.yp.pm 2016-06-13 22:25:22 +0000 It appears the information has been provided. 79489 7 tracy.graydon 2018-02-16 19:34:54 +0000 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. 79644 8 stephano 2018-03-01 14:24:30 +0000 Setting this to undecided 2.6 so we can discuss in bug triage. 79648 9 richard.purdie 2018-03-01 15:44:37 +0000 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.