All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
	"rpjday@crashcourse.ca" <rpjday@crashcourse.ca>,
	Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] repost: how to create a SPDX "notice file" from a build?
Date: Sat, 23 Nov 2019 12:01:33 +0000	[thread overview]
Message-ID: <a126a3ecf7d93e638dc650ef92dfc2fdcebd221b.camel@linuxfoundation.org> (raw)
In-Reply-To: <02bee54a-3a3b-aac2-812d-50b5c395aaa3@gmail.com>

On Fri, 2019-11-22 at 09:59 -0800, akuster808 wrote:
> 
> 
> On 11/22/19 9:03 AM, rpjday@crashcourse.ca wrote:
> > On Fri, 22 Nov 2019, Robert P. J. Day wrote:
> > 
> > 
> > /////////// end /////////
> > 
> >   i have absolutely no idea what to think of this, and am open to
> > suggestions. does anyone have a working scenario to simply
> > demonstrate
> > the usage of spdx.bbclass?
>  
> Would you mind opening a Yocto defect.

That code hasn't been touched in a while and needs some serious
attention. The underlying tools and processes have changed so much it
may be a case of starting again and we should perhaps consider removing
that class...

Cheers,

Richard


  reply	other threads:[~2019-11-23 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 14:54 repost: how to create a SPDX "notice file" from a build? rpjday
2019-11-22 17:03 ` rpjday
2019-11-22 17:57   ` [yocto] " Khem Raj
2019-11-22 17:59   ` akuster808
2019-11-23 12:01     ` Richard Purdie [this message]
2019-11-23 12:02       ` rpjday
2019-11-23 15:53       ` Mark Hatle
2019-11-24 10:11       ` rpjday
2019-11-24 16:37         ` Mark Hatle

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=a126a3ecf7d93e638dc650ef92dfc2fdcebd221b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.com \
    --cc=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.