Re: [oe] [RFC] Using OE with Fossology.
On 09.02.18 17:29, Peter Kjellerstedt wrote: >> -Original Message- >> From: openembedded-devel-boun...@lists.openembedded.org >> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of >> Beth 'pidge' Flanagan >> Sent: den 8 februari 2018 17:21 >> To: openembedded-devel@lists.openembedded.org >> Subject: [oe] [RFC] Using OE with Fossology. >> >> All, >> >> I wanted to make folks aware that we've released a new layer to do >> automated fossology runs within OE. The old spdx.bbclass is bitrot and >> we needed something to make some of our license clearance and tracking >> easier to manage. >> >> http://layers.openembedded.org/layerindex/branch/master/layer/meta-license-tools/ >> >> This layer takes patched archives created by the source archiver during >> the build and, using a utility we wrote called fossup, sends them on to >> a fossology instance for out of build scanning. >> >> The impact on build times is relatively small. If you want to use it, >> you'll need to install fossup (https://gitlab.com/toganlabs/fossup), set > > Any particular reason you don't provide a recipe for fossup in the > layer so you can avoid having to install it manually? Yes. Because a fossup and a fossology instance is generally something that I just assume is provided (username/passwd/URL etc all need configuring). I don't see an issue in providing that recipe, though, but for my use cases, it's going to be something I have already installed and configured for my fossology instances outside of the build process. I'll be happy to work up a recipe for it when I've a moment (or a patch is always welcome). -b > >> up the fossup rc file to point to your fossology instance (all of this >> is in the README), and ensure that the bits needed for an archiver build >> are included in your local.conf >> >> Typically this will look like the following: >> >> INHERIT += "archiver" >> ARCHIVER_MODE[src] = "patched" >> ARCHIVER_MODE[diff] = "0" >> ARCHIVER_MODE[dumpdata] = "0" >> ARCHIVER_MODE[recipe] = "1" >> COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*' >> COPYLEFT_LICENSE_EXCLUDE = 'CLOSED Proprietary' >> COPYLEFT_RECIPE_TYPES = 'target' >> INHERIT += "fossology" >> >> Feedback welcome of course. >> >> -b >> >> >> Beth 'pidge' Flanagan >> pi...@toganlabs.com > > //Peter > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [RFC] Using OE with Fossology.
> -Original Message- > From: openembedded-devel-boun...@lists.openembedded.org > [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of > Beth 'pidge' Flanagan > Sent: den 8 februari 2018 17:21 > To: openembedded-devel@lists.openembedded.org > Subject: [oe] [RFC] Using OE with Fossology. > > All, > > I wanted to make folks aware that we've released a new layer to do > automated fossology runs within OE. The old spdx.bbclass is bitrot and > we needed something to make some of our license clearance and tracking > easier to manage. > > http://layers.openembedded.org/layerindex/branch/master/layer/meta-license-tools/ > > This layer takes patched archives created by the source archiver during > the build and, using a utility we wrote called fossup, sends them on to > a fossology instance for out of build scanning. > > The impact on build times is relatively small. If you want to use it, > you'll need to install fossup (https://gitlab.com/toganlabs/fossup), set Any particular reason you don't provide a recipe for fossup in the layer so you can avoid having to install it manually? > up the fossup rc file to point to your fossology instance (all of this > is in the README), and ensure that the bits needed for an archiver build > are included in your local.conf > > Typically this will look like the following: > > INHERIT += "archiver" > ARCHIVER_MODE[src] = "patched" > ARCHIVER_MODE[diff] = "0" > ARCHIVER_MODE[dumpdata] = "0" > ARCHIVER_MODE[recipe] = "1" > COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*' > COPYLEFT_LICENSE_EXCLUDE = 'CLOSED Proprietary' > COPYLEFT_RECIPE_TYPES = 'target' > INHERIT += "fossology" > > Feedback welcome of course. > > -b > > > Beth 'pidge' Flanagan > pi...@toganlabs.com //Peter -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [RFC] Using OE with Fossology.
All, I wanted to make folks aware that we've released a new layer to do automated fossology runs within OE. The old spdx.bbclass is bitrot and we needed something to make some of our license clearance and tracking easier to manage. http://layers.openembedded.org/layerindex/branch/master/layer/meta-license-tools/ This layer takes patched archives created by the source archiver during the build and, using a utility we wrote called fossup, sends them on to a fossology instance for out of build scanning. The impact on build times is relatively small. If you want to use it, you'll need to install fossup (https://gitlab.com/toganlabs/fossup), set up the fossup rc file to point to your fossology instance (all of this is in the README), and ensure that the bits needed for an archiver build are included in your local.conf Typically this will look like the following: INHERIT += "archiver" ARCHIVER_MODE[src] = "patched" ARCHIVER_MODE[diff] = "0" ARCHIVER_MODE[dumpdata] = "0" ARCHIVER_MODE[recipe] = "1" COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*' COPYLEFT_LICENSE_EXCLUDE = 'CLOSED Proprietary' COPYLEFT_RECIPE_TYPES = 'target' INHERIT += "fossology" Feedback welcome of course. -b Beth 'pidge' Flanagan pi...@toganlabs.com -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
