8652 2015-11-05 12:46:53 +0000 meta/recipes-devtools/ruby/ uses --disable-versioned-paths, but no such option exists 2016-10-17 17:19:09 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.2 x86 Multiple RESOLVED OBSOLETE Low minor 2.2 M1 1 ulfalizer ulfalizer leonardo.sandoval.gonzalez meta.mr.watcher meta.watcher sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 56223 0 ulfalizer 2015-11-05 12:46:53 +0000 This might be a copy-paste error from the meta-openembedded Ruby recipe, which adds --disable-versioned-paths via a patch. (That patch contains a bug as of writing: http://lists.openembedded.org/pipermail/openembedded-devel/2015-November/104350.html) 62238 1 alejandro.hernandez 2016-05-17 01:45:32 +0000 Hello, Is disable-versioned-paths really necessary?, it was first introduced on meta-oe on commit: http://cgit.openembedded.org/meta-openembedded/commit/?id=5df465fcb72f8ec3417951f67cba0cbc73e23f5c Although it does not explain why it was introduced in the first place, it just says it comes from Fedora. An then it was deleted on commit: http://cgit.openembedded.org/meta-openembedded/commit/?id=9667f17d6ec3ca1b719d230e69569cf57c766a4d Where a bunch of other patches were dropped along with it, it seems to me that it might not be necessary, I just ran a build and I see no errors on do_configure either. Now, if it is necessary I will bring the patch back from ruby 1.9.3 fix it with the patch shown on this thread and rebase it. 63771 2 sgw 2016-07-08 20:37:35 +0000 I am closing this bug as obsolete as it does not seem that we are support Ruby 1.9.3 and the patches have been removed from both oe-core and meta-openembedded/meta-ruby. If there is still action required, please reopen this bug and provide more details.