All of
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <>
To: "Robert P. J. Day" <>
Subject: Re: [meta-virtualization] what is the state of meta-cloud-services, re: chef/puppet/ruby recipes?
Date: Tue, 5 Jan 2021 16:27:47 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Jan 2, 2021 at 9:20 AM Robert P. J. Day <> wrote:
> 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?

I honestly can't say. I did little but review and merge the ruby
changes. There was a primary author for the changes, and I haven't
heard from them for some time.

I don't recall them really being used in the -native variant, so it
could / should probably just be a mass removal.

Do you have a use case on the -native side of things ?


> rday

- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

  reply	other threads:[~2021-01-05 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 18:28 what is the state of meta-cloud-services, re: chef/puppet/ruby recipes? Robert P. J. Day
2020-12-27 19:20 ` [meta-virtualization] " Bruce Ashfield
2021-01-02 14:20   ` Robert P. J. Day
2021-01-05 21:27     ` Bruce Ashfield [this message]
2021-01-02 20:07   ` Robert P. J. Day
2021-01-05 21:31     ` Bruce Ashfield

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:

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

  git send-email \
    --in-reply-to='' \ \ \ \

* 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.