Generating license/manifest for a specific layer?

Generating license/manifest for a specific layer?

[Michael Habibi]

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

Our use case is to capture the license files, manifest (package/version),
and download information only for packages we modify/add. We use our own
layer to modify/add packages, everything coming from standard Yocto layers
are untouched.

Is there a way to generate this information on a layer-by-layer basis,
instead of a full manifest that includes all standard, unmodified packages?

[-- Attachment #2: Type: text/html, Size: 431 bytes --]

Re: Generating license/manifest for a specific layer?

[Beth Flanagan]

On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi <mikehabibi@gmail.com> wrote:
> Our use case is to capture the license files, manifest (package/version),
> and download information only for packages we modify/add. We use our own
> layer to modify/add packages, everything coming from standard Yocto layers
> are untouched.
>
> Is there a way to generate this information on a layer-by-layer basis,
> instead of a full manifest that includes all standard, unmodified packages?

The easy (cheating) way, would be to modify the tmp/deploy/licenses
artifact post build (I do it to remove -native- and -cross- from
things I distribute as I'm not actually distributing them) or put in a
post do_rootfs function that does it.

I guess my question would be (and this is less a technical question
and more of a legal one) is why would you want to only include a
manifest for only part of what you're distributing (or am I
misunderstanding what you're trying to do here?)

-b
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: Generating license/manifest for a specific layer?

[Ulf Samuelsson]

I have been working on a release-notes bbclass which will for each recipe included in am image extract stuff like package name, license info, cve info, SUMMARY, DESCRIPTION etc. and generate LaTex files.
repo diffmanifests is used to extract the difference between a previous manifest and the current manifest. 
Each patch committed has a JIRA ticket number, and a LaTex file is generated with a symbolic link to our JIRA server.
Everything is collected by a separate project, and once the LaTex files are complete,
I only have to do 
make <product>-release-notes.pdf.

Once it is merged locally, I am considering upstreaming.

Best Regards,
Ulf Samuelsson

> 11 juni 2018 kl. 15:46 skrev Michael Habibi <mikehabibi@gmail.com>:
> 
> Our use case is to capture the license files, manifest (package/version), and download information only for packages we modify/add. We use our own layer to modify/add packages, everything coming from standard Yocto layers are untouched.
> 
> Is there a way to generate this information on a layer-by-layer basis, instead of a full manifest that includes all standard, unmodified packages?
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Generating license/manifest for a specific layer?

[Michael Habibi]

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

Beth,

This is for internal consumption. We want to be able to generate a full
manifest, and also one that reflects how we diverged from base Yocto
distribution.

On Mon, Jun 11, 2018 at 10:55 AM Beth Flanagan <pidge@toganlabs.com> wrote:

> On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi <mikehabibi@gmail.com>
> wrote:
> > Our use case is to capture the license files, manifest (package/version),
> > and download information only for packages we modify/add. We use our own
> > layer to modify/add packages, everything coming from standard Yocto
> layers
> > are untouched.
> >
> > Is there a way to generate this information on a layer-by-layer basis,
> > instead of a full manifest that includes all standard, unmodified
> packages?
>
> The easy (cheating) way, would be to modify the tmp/deploy/licenses
> artifact post build (I do it to remove -native- and -cross- from
> things I distribute as I'm not actually distributing them) or put in a
> post do_rootfs function that does it.
>
> I guess my question would be (and this is less a technical question
> and more of a legal one) is why would you want to only include a
> manifest for only part of what you're distributing (or am I
> misunderstanding what you're trying to do here?)
>
> -b
> >
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>

[-- Attachment #2: Type: text/html, Size: 2030 bytes --]

Re: Generating license/manifest for a specific layer?

[Beth Flanagan]

Ok, I guess my question there then would be is how you'd determine
where a recipe "lived". Like, if meta-foo has a bbappends for
something in core, would you include it or not in your manifest?

If so, then taking the original manifest and just doing some text
manipulation in a ROOTFS_POSTPROCESS_COMMAND would be the way I'd
probably look at tackling it.

On Wed, Jun 13, 2018 at 2:42 PM, Michael Habibi <mikehabibi@gmail.com> wrote:
> Beth,
>
> This is for internal consumption. We want to be able to generate a full
> manifest, and also one that reflects how we diverged from base Yocto
> distribution.
>
> On Mon, Jun 11, 2018 at 10:55 AM Beth Flanagan <pidge@toganlabs.com> wrote:
>>
>> On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi <mikehabibi@gmail.com>
>> wrote:
>> > Our use case is to capture the license files, manifest
>> > (package/version),
>> > and download information only for packages we modify/add. We use our own
>> > layer to modify/add packages, everything coming from standard Yocto
>> > layers
>> > are untouched.
>> >
>> > Is there a way to generate this information on a layer-by-layer basis,
>> > instead of a full manifest that includes all standard, unmodified
>> > packages?
>>
>> The easy (cheating) way, would be to modify the tmp/deploy/licenses
>> artifact post build (I do it to remove -native- and -cross- from
>> things I distribute as I'm not actually distributing them) or put in a
>> post do_rootfs function that does it.
>>
>> I guess my question would be (and this is less a technical question
>> and more of a legal one) is why would you want to only include a
>> manifest for only part of what you're distributing (or am I
>> misunderstanding what you're trying to do here?)
>>
>> -b
>> >
>> > --
>> > _______________________________________________
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>> >

Re: Generating license/manifest for a specific layer?

[Michael Habibi]

[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]

So to clarify your question, basically everything we would want in the
custom manifest would be in our own layer: both bbappends and new bb
recipes. Given that, you think I could still modify it like you suggest to
get what I want?

On Wed, Jun 13, 2018 at 8:59 AM Beth Flanagan <pidge@toganlabs.com> wrote:

> Ok, I guess my question there then would be is how you'd determine
> where a recipe "lived". Like, if meta-foo has a bbappends for
> something in core, would you include it or not in your manifest?
>
> If so, then taking the original manifest and just doing some text
> manipulation in a ROOTFS_POSTPROCESS_COMMAND would be the way I'd
> probably look at tackling it.
>
> On Wed, Jun 13, 2018 at 2:42 PM, Michael Habibi <mikehabibi@gmail.com>
> wrote:
> > Beth,
> >
> > This is for internal consumption. We want to be able to generate a full
> > manifest, and also one that reflects how we diverged from base Yocto
> > distribution.
> >
> > On Mon, Jun 11, 2018 at 10:55 AM Beth Flanagan <pidge@toganlabs.com>
> wrote:
> >>
> >> On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi <mikehabibi@gmail.com>
> >> wrote:
> >> > Our use case is to capture the license files, manifest
> >> > (package/version),
> >> > and download information only for packages we modify/add. We use our
> own
> >> > layer to modify/add packages, everything coming from standard Yocto
> >> > layers
> >> > are untouched.
> >> >
> >> > Is there a way to generate this information on a layer-by-layer basis,
> >> > instead of a full manifest that includes all standard, unmodified
> >> > packages?
> >>
> >> The easy (cheating) way, would be to modify the tmp/deploy/licenses
> >> artifact post build (I do it to remove -native- and -cross- from
> >> things I distribute as I'm not actually distributing them) or put in a
> >> post do_rootfs function that does it.
> >>
> >> I guess my question would be (and this is less a technical question
> >> and more of a legal one) is why would you want to only include a
> >> manifest for only part of what you're distributing (or am I
> >> misunderstanding what you're trying to do here?)
> >>
> >> -b
> >> >
> >> > --
> >> > _______________________________________________
> >> > yocto mailing list
> >> > yocto@yoctoproject.org
> >> > https://lists.yoctoproject.org/listinfo/yocto
> >> >
>

[-- Attachment #2: Type: text/html, Size: 3333 bytes --]