Re: [meta-virtualization] what is the state of meta-cloud-services, re: chef/puppet/ruby recipes?

From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] what is the state of meta-cloud-services, re: chef/puppet/ruby recipes?
Date: Sat, 2 Jan 2021 09:20:14 -0500 (EST)	[thread overview]
Message-ID: <4720fd3-e8d0-544f-2388-15f275d631@crashcourse.ca> (raw)
In-Reply-To: <CADkTA4Nf59A4F_JrPOtv77FK57nNEVjEvirhuegmWc=WwJzyhQ@mail.gmail.com>

On Sun, 27 Dec 2020, Bruce Ashfield wrote:

... snip ...

> No one has done much with the ruby support in quite some time, so it
> would need work as well. I thought there was a meta-ruby floating
> around, but I couldn't find it on the layerindex, so it looks like
> just oe-core + some work would be required.

  dumb question alert: i'm currently going through all of the ruby
recipes in meta-openstack, doing the occasional fixup to get them to
build on the master branch, and i can see that all(?) of those recipes
define a SRC_URI that downloads a proper .gemspec file for each
recipe, which allows the recipe to build.

  *however*, even though a number of those recipes BBCLASSEXTEND to
class "native", it's not possible to build the native variants as the
error is that there is no gemspec file for the native variant. which
is why i get:

  $ bitbake yard-native
  ...
  Log data follows:
  | DEBUG: Executing shell function do_compile
  | ERROR:  Gemspec file not found: yard-native.gemspec
  ... snip ...

what's the magic to build native ruby recipes? does one actually have
to define a distinct native version of the gemspec file for each
recipe?

rday