(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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137509): https://lists.openembedded.org/g/openembedded-core/message/137509 Mute This Topic: https://lists.openembedded.org/mt/73291165/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
