Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Mark Asselstine <mark.asselstine@windriver.com>,
	 Martin.Jansa@gmail.com,
	openembedded-devel@lists.openembedded.org
Subject: Re: [[meta-ruby][PATCH 1/2] ruby.bbclass: handle new installation directories
Date: Thu, 20 Aug 2015 14:51:17 -0700	[thread overview]
Message-ID: <55D64BD5.2080203@gmail.com> (raw)
In-Reply-To: <1440102538-1561-1-git-send-email-mark.asselstine@windriver.com>

Thanks

- Armin

On 08/20/2015 01:28 PM, Mark Asselstine wrote:
> It appears that newer versions of ruby produce additional directories
> which were not previously handled by the ruby bbclass, specifically
> 'build_info' and 'extensions'. This is currently resulting in QA
> errors/warnings such as:
>
> ERROR: QA Issue: puppet: Files/directories were installed but not shipped in any package:
>    /usr/lib64/ruby/gems/2.2.0/build_info
>    /usr/lib64/ruby/gems/2.2.0/extensions
> Please set FILES such that these items are packaged. Alternatively if they are unneeded,
> avoid installing them or delete them within do_install. [installed-vs-shipped]
>
> Add these to our FILES in the bbclass such that they will packaged.
>
> NOTE: several files may exist in the extensions directory such as
> gem.build_complete and mkmf.log that we can most likely remove during
> do_install. Since ruby installs these by default they have been left
> in case their existence is used as some type of stampfile or similar.
>
> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
> ---
>   meta-ruby/classes/ruby.bbclass | 6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/meta-ruby/classes/ruby.bbclass b/meta-ruby/classes/ruby.bbclass
> index 9c4fcf9..ef844f2 100644
> --- a/meta-ruby/classes/ruby.bbclass
> +++ b/meta-ruby/classes/ruby.bbclass
> @@ -111,6 +111,10 @@ FILES_${PN}-dbg += " \
>           ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/gems/*/*/*/.debug \
>           ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/gems/*/*/*/*/.debug \
>           ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/gems/*/*/*/*/*/.debug \
> +        ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/extensions/*/*/.debug \
> +        ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/extensions/*/*/*/.debug \
> +        ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/extensions/*/*/*/*/.debug \
> +        ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/extensions/*/*/*/*/*/.debug \
>           "
>
>   FILES_${PN} += " \
> @@ -118,6 +122,8 @@ FILES_${PN} += " \
>           ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/cache \
>           ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/bin \
>           ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/specifications \
> +        ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/build_info \
> +        ${libdir}/ruby/gems/${RUBY_GEM_VERSION}/extensions \
>           "
>
>   FILES_${PN}-doc += " \
>


      parent reply	other threads:[~2015-08-20 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 20:28 [[meta-ruby][PATCH 1/2] ruby.bbclass: handle new installation directories Mark Asselstine
2015-08-20 20:28 ` [[meta-ruby][PATCH 2/2] bundler: remove broad FILES definition Mark Asselstine
2015-08-20 21:51 ` akuster808 [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=55D64BD5.2080203@gmail.com \
    --to=akuster808@gmail.com \
    --cc=Martin.Jansa@gmail.com \
    --cc=mark.asselstine@windriver.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox