Running nanoc with Ruby, which has been merged with USE=-yaml results in nanoc complaining like this --snip-- nanoc -l cs testing █ /usr/lib64/ruby/1.9.1/yaml.rb:56:in `<top (required)>': It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. create config.yaml create Rules create content/index.html create content/stylesheet.css create layouts/default.html Created a blank nanoc site at 'testing'. Enjoy! --snap-- Therefor the ebuild should require dev-lang/ruby to be build with USE=yaml or at least issue some ewarn. (BTW, nanoc is @3.4.2 while portage is at 3.4.0) Reproducible: Always Steps to Reproduce: 1. USE=-yaml (or defined elsewhere) ruby nanoc 2. nanoc 3. Actual Results: Warning as shown above
Damn, just found it should of course read 'www-apps/nanoc' in title, sorry.
I'm wondering if we should not fix this by making yaml mandatory in dev-lang/ruby, since there will be many packages that depend on yaml being present and it really makes no sense to me to have a complicated virtual just for that. @ruby: any feedback from your side? I'm not sure why we added the yaml USE flag in the first place?
I've just tested this with ruby-1.9.3_p448-r1 and nanoc 3.6.4 and I could not reproduce this issue. Do you still see this?
I spoke too soon. I can reproduce this, but it is also clear that this is a harmless warning. In this specific case the 'syck' engine is still being used and YAML support should work as expected, but you get the warning because 'syck' is not explicitly requested.
