All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: how to identify/remove all ruby-related content from an image?
Date: Sun, 26 Apr 2020 16:40:31 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.2004261634170.91219@localhost.localdomain> (raw)


  (note: i think i discovered the simplest way to do this but ...
onward.)

  given an OE image based on some old YP versions (mostly morty/2.2),
there is a maddeningly intermittent build issue with one or the other
of a small number of ruby gems, so my initial idea is, for now, to
just remove all ruby-related content from the image and see if it
builds reliably.

  the idea is to remove any ruby-based recipes, then build and clean
over and over to see if the build error goes away. the ruby stuff is
non-critical stuff (chef and puppet, among other things), but the
current image drags in some 9 or 10 layers, and all sorts of custom
packagegroups, so i was looking for the quickest way to identify
what's based on ruby, and was ready to use "bitbake -g" to construct a
dependency graph and so on, until it occurred to me ...

 ... why not just blacklist ruby in local.conf, then start removing
whatever breaks because of that? is that the easiest way to do this? i
just don't want to claw my way through numerous layers and
packagegroups to figure this out.

rday

                 reply	other threads:[~2020-04-26 20:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.21.2004261634170.91219@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@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 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.