6c3cdb04ac
Switch to YAML::XS to work around insanity in YAML::Mo. Closes : #657533
...
https://rt.cpan.org/Ticket/Display.html?id=74487
Gave up trying to support multiple YAML backends. The XS one requires ugly
manual encoding to get unicode right, and doesn't allow dumping yaml
fragments w/o the yaml header, but at least it doesn't randomly crash
on import like YAML::Mo has started to.
2012-01-28 22:36:14 -04:00
97a8d30dc1
Support YAML::XS by not passing decoded unicode to Load. Closes : #625713
2011-05-12 17:50:25 -04:00
0219529699
fix unicode with YAML::Syck
...
Syck-- it doesn't use unicode by default?! Hello, 2010 calling..
2010-03-24 16:19:50 -04:00
eb06a01355
use perl YAML for dumping
...
Only it understands $YAML::UseHeader
2010-03-24 16:12:35 -04:00
3166479fe4
fall back from YAML::Any to just YAML
...
for portabilty to old YAML in Debian stable that lacks the former.
2010-03-24 14:53:32 -04:00
271449062a
use YAML::Any to allow faster versions to be used if available
2010-03-24 14:30:38 -04:00
dc128dd829
fix newlines in commented defaults
2010-03-19 17:54:58 -04:00
3b08789e6f
load YAML on demand
...
so as not to break test suite if YAML is not avilable
2010-03-19 16:09:07 -04:00
bba513a3e5
Add support for setup files written in YAML.
...
Not the default. (Yet?)
2010-03-19 15:52:53 -04:00
Joey Hess
Joey Hess