Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: Add SRC_URI and HOMEPAGE to manifest
Date: Tue, 14 Nov 2017 17:17:38 +0000	[thread overview]
Message-ID: <1510679858.3952.124.camel@linuxfoundation.org> (raw)
In-Reply-To: <20171114170528.5645-1-sgw@linux.intel.com>

On Tue, 2017-11-14 at 09:05 -0800, Saul Wold wrote:
> This will allow tools to be developed that create manifest based BOMs
> with detailed information.
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/classes/package.bbclass | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/classes/package.bbclass
> b/meta/classes/package.bbclass
> index 2053d46395a..c2410238682 100644
> --- a/meta/classes/package.bbclass
> +++ b/meta/classes/package.bbclass
> @@ -1387,6 +1387,8 @@ python emit_pkgdata() {
>          write_if_exists(sf, pkg, 'LICENSE')
>          write_if_exists(sf, pkg, 'DESCRIPTION')
>          write_if_exists(sf, pkg, 'SUMMARY')
> +        write_if_exists(sf, pkg, 'SRC_URI')
> +        write_if_exists(sf, pkg, 'HOMEPAGE')
>          write_if_exists(sf, pkg, 'RDEPENDS')
>          rprov = write_if_exists(sf, pkg, 'RPROVIDES')
>          write_if_exists(sf, pkg, 'RRECOMMENDS')

This was already proposed once and rejected as its using the interface
for something it really wasn't designed for :/.

Cheers,

Richard


      reply	other threads:[~2017-11-14 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 17:05 [PATCH] package.bbclass: Add SRC_URI and HOMEPAGE to manifest Saul Wold
2017-11-14 17:17 ` Richard Purdie [this message]

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=1510679858.3952.124.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.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