Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <bluelightning@bluelightning.org>
To: Joshua Watt <jpewhacker@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	Jose Quaresma <quaresma.jose@gmail.com>,
	openembedded-core@lists.openembedded.org
Cc: Steve Sakoman <sakoman@gmail.com>,
	OE-core <openembedded-core@lists.openembedded.org>,
	Saul Wold <Saul.Wold@windriver.com>,
	Andres Beltran <abeltran@linux.microsoft.com>
Subject: Re: [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship
Date: Tue, 16 Nov 2021 11:44:31 +1300	[thread overview]
Message-ID: <3381838.aeNJFYEL58@linc> (raw)
In-Reply-To: <9c6aa6d7-ddb5-0bab-8639-063e71379101@windriver.com>

On Tuesday, 9 November 2021 08:01:38 NZDT Saul Wold wrote:
> On 11/4/21 2:20 PM, Joshua Watt wrote:
> > On 11/4/21 3:50 PM, Richard Purdie wrote:
> >> On Thu, 2021-11-04 at 15:45 -0500, Joshua Watt wrote:
> >>> On 11/4/21 3:43 PM, Richard Purdie wrote:
> >>>> On Thu, 2021-11-04 at 20:00 +0000, Jose Quaresma wrote:
> >>>>> Richard Purdie <richard.purdie@linuxfoundation.org> escreveu no dia
> >>>>> quinta,
> >>>>> 
> >>>>> 28/10/2021 à(s) 21:58:
> >>>>>> On Thu, 2021-10-28 at 08:47 -1000, Steve Sakoman wrote:
> >>>>>>> On Tue, Oct 26, 2021 at 10:41 PM Jose Quaresma
> >>>>>>> <quaresma.jose@gmail.com>
> >>>>>> 
> >>>>>> wrote:
> >>>>>>>> Hi all,
> >>>>>>>> 
> >>>>>>>> There are any plans or is it possible to backport the SBOM/SPDX
> >>>>>>>> to the
> >>>>>> 
> >>>>>> dunfell branch?
> >>>>>> 
> >>>>>>> I'm going to yield to Saul as to whether he thinks this is
> >>>>>>> desirable/possible or not.
> >>>>>> 
> >>>>>> The packagedata changes are pretty invasive unfortunately and
> >>>>>> likely not
> >>>>>> something you're going to want in dunfell sadly.
> >>>>> 
> >>>>> Thanks for the clarification.
> >>>> 
> >>>> I have been thinking a bit more about this. I did wonder if we
> >>>> should consider a
> >>>> mixin layer of some kind for it that could work with dunfell?
> >>>> 
> >>>> We could host it, it is just a question of writing the mixin layer and
> >>>> maintaining it.
> >>> 
> >>> I don't think it's going to be possible with a pure mixin layer, since
> >>> it relies on the extended package data?
> >> 
> >> I suspect that could perhaps be patched in through a layer though? You
> >> might
> >> choose to drop the compression piece or do it differently for the
> >> backport?
> > 
> > I'm not sure if a layer could hook in well enough to get the data
> > needed...  maybe worth an experiment though
> 
> Yeah, I am not sure an mixin could track the changes for package.bbclass
> 
> > With a backport, I would probably either use GZip compression or no
> > compression. The zstd compression was designed as a drop in replacement
> > for Gzip if we wanted to go that route.
> 
> I will say that we did something similar with Hardknott for WRLinux, but
> did not propose it upstream as Hardknott was knot going to be supported
> longer term.
> 
> Having the spdx class standalone with the correctly backported changes
> seems to be working

FYI Andres and I have done this backport to dunfell - should I post it? That 
said, I did just take the hit on some of the invasive parts (e.g. LICENSE 
value changes). I think given regulatory requirements this is important for 
lots of folks, so we probably need to do something here. Happy to be part of 
it.

Cheers
Paul






  reply	other threads:[~2021-11-15 22:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27  1:30 [PATCH 0/3] SPDX: Add annotations to relationship Saul Wold
2021-10-27  1:30 ` [PATCH v2 1/3] spdx.py: Add annotation " Saul Wold
2021-10-27  1:30 ` [PATCH v2 2/3] create-spdx: add create_annotation function Saul Wold
2021-10-27  1:30 ` [PATCH v2 3/3] create-spdx: cross recipes are native also Saul Wold
2021-10-27  8:40 ` [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship Jose Quaresma
2021-10-28 18:47   ` Steve Sakoman
2021-10-28 20:58     ` Richard Purdie
2021-11-04 20:00       ` Jose Quaresma
2021-11-04 20:43         ` Richard Purdie
2021-11-04 20:45           ` Joshua Watt
2021-11-04 20:50             ` Richard Purdie
2021-11-04 21:20               ` Joshua Watt
2021-11-08 19:01                 ` Saul Wold
2021-11-15 22:44                   ` Paul Eggleton [this message]
2021-11-16 11:14                     ` Jose Quaresma
2021-11-16 16:39                     ` Saul Wold
2021-11-16 16:57                       ` Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3381838.aeNJFYEL58@linc \
    --to=bluelightning@bluelightning.org \
    --cc=Saul.Wold@windriver.com \
    --cc=abeltran@linux.microsoft.com \
    --cc=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quaresma.jose@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sakoman@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox